Using .NET 1.1

[Anthony Gallagher]

I have been browsing around Microsoft's site trying to get answers to
the following questions:
1) If VS .NET 2002 is installed on the computer, is it possible to
install the .NET 1.1 Framework+SDK and get VS .NET 2002 to use them?
2) Are there any benefits to doing so?
3) If I have no use for J#, are there any compelling reasons to move
from VS .NET 2002 to 2003, specially if it is possible to use .NET 1.1
with VS .NET 2002?

Anthony

[Tomas Restrepo \(MVP\)]

Hi Anthony,

I have been browsing around Microsoft's site trying to get answers to
the following questions:
1) If VS .NET 2002 is installed on the computer, is it possible to
install the .NET 1.1 Framework+SDK and get VS .NET 2002 to use them?
No.
2) Are there any benefits to doing so? Not really, since you can't :)
3) If I have no use for J#, are there any compelling reasons to move
from VS .NET 2002 to 2003, specially if it is possible to use .NET 1.1
with VS .NET 2002?

There are quite a few. For example, VC++ is much improved and has now tons
of new support for ISO standard C++ compliance. There's also support in some
of the other products for things like mobile development, etc.

--
Tomas Restrepo
to****@mvps.org

[Anthony Gallagher]

Thanks for the response Tomas.
I have another question:
Is it at least possible to replace the .NET Framework 1.0 with the .NET
1.1 Framework (not SDK) on a machine with VS .NET 2002? I would assume
so since people talk about VS .NET 2002 and VS .NET 2003 coexisting on a
single machine, but I'm not sure.

Thanks,

Anthony

PS: It seems somehow harsh that MS already made VS .NET 2002 obsolete
one year after releasing it. What happened to good old Service Packs a
la VS 6.0?

Tomas Restrepo (MVP) wrote:

Hi Anthony,

I have been browsing around Microsoft's site trying to get answers to
the following questions:
1) If VS .NET 2002 is installed on the computer, is it possible to
install the .NET 1.1 Framework+SDK and get VS .NET 2002 to use them?

No.

2) Are there any benefits to doing so?

Not really, since you can't :)

3) If I have no use for J#, are there any compelling reasons to move
from VS .NET 2002 to 2003, specially if it is possible to use .NET 1.1
with VS .NET 2002?

There are quite a few. For example, VC++ is much improved and has now tons
of new support for ISO standard C++ compliance. There's also support in some
of the other products for things like mobile development, etc.

[Tomas Restrepo \(MVP\)]

Anthony,

Is it at least possible to replace the .NET Framework 1.0 with the .NET
1.1 Framework (not SDK) on a machine with VS .NET 2002?
Well, that wouldn't quite work, since you need the 1.0 framework to build
applications with VS.NET 2002 ;)
I would assume
so since people talk about VS .NET 2002 and VS .NET 2003 coexisting on a
single machine, but I'm not sure.

They are built to coexist. You can have both of them installed at the same
time, and in most cases apps built with 1.0 will run agains 1.0, while those
built with 1.1 will run against 1.1 [1]. Also, both VS.NET versions coexist
on the same machine with no issues, too.
[1] minor exception is asp.net, but that's easy to arrange, too, as long as
you set things up properly.

--
Tomas Restrepo
to****@mvps.org

[Carl Daniel [VC++ MVP]]

No, your 1.0 app will work on the 1.1 framework through a mechanism called
"fusion".

It's only for developmentt that there's a hard dependency: if you're using
VS.NET 2002, you're targeting the 1.0 runtime. If you're using VS.NET 2003
you're targeting the 1.1 framework.

-cd

Anthony Gallagher wrote:

Wow, that's a little wild. I hope they MS changes their strategy for
the future versions of the .NET Framework, or people are going to
have to
have every single version installed!
So basically, if somebody has the .NET Framework 1.1 installed on
their machine, and I give them my app written using VS .NET 2002, it
won't
work?? Why couldn't MS follow the Sun strategy with the JVM's and make
things compatible?

Anthony

Tomas Restrepo (MVP) wrote:

Anthony,

Is it at least possible to replace the .NET Framework 1.0 with the
.NET
1.1 Framework (not SDK) on a machine with VS .NET 2002?

Well, that wouldn't quite work, since you need the 1.0 framework to
build applications with VS.NET 2002 ;)

I would assume
so since people talk about VS .NET 2002 and VS .NET 2003 coexisting
on a single machine, but I'm not sure.

They are built to coexist. You can have both of them installed at
the same time, and in most cases apps built with 1.0 will run agains
1.0, while those built with 1.1 will run against 1.1 [1]. Also, both
VS.NET versions coexist on the same machine with no issues, too.
[1] minor exception is asp.net, but that's easy to arrange, too, as
long as you set things up properly.

[Anthony Gallagher]

I see. That makes more sense. Naturally an app made with VS.NET 2003
will not work on a machine with only the 1.0 framework, correct?

Anthony

Carl Daniel [VC++ MVP] wrote:

No, your 1.0 app will work on the 1.1 framework through a mechanism called
"fusion".

It's only for developmentt that there's a hard dependency: if you're using
VS.NET 2002, you're targeting the 1.0 runtime. If you're using VS.NET 2003
you're targeting the 1.1 framework.

-cd

Anthony Gallagher wrote:

Wow, that's a little wild. I hope they MS changes their strategy for
the future versions of the .NET Framework, or people are going to
have to
have every single version installed!
So basically, if somebody has the .NET Framework 1.1 installed on
their machine, and I give them my app written using VS .NET 2002, it
won't
work?? Why couldn't MS follow the Sun strategy with the JVM's and make
things compatible?

Anthony

Tomas Restrepo (MVP) wrote:

Anthony,

Is it at least possible to replace the .NET Framework 1.0 with the
.NET
1.1 Framework (not SDK) on a machine with VS .NET 2002?
Well, that wouldn't quite work, since you need the 1.0 framework to
build applications with VS.NET 2002 ;)

I would assume
so since people talk about VS .NET 2002 and VS .NET 2003 coexisting
on a single machine, but I'm not sure.
They are built to coexist. You can have both of them installed at
the same time, and in most cases apps built with 1.0 will run agains
1.0, while those built with 1.1 will run against 1.1 [1]. Also, both
VS.NET versions coexist on the same machine with no issues, too.
[1] minor exception is asp.net, but that's easy to arrange, too, as
long as you set things up properly.

[Tomas Restrepo \(MVP\)]

Hi Anthony,

I see. That makes more sense. Naturally an app made with VS.NET 2003
will not work on a machine with only the 1.0 framework, correct?

Ahh, tricky question! Yes and no. As long as you don't use any v1.1-specific
functionality, you can add a special ssection to your app.config file and
have it run against 1.0. (see [3]) However, for MC++ apps, things are
trickier, since there was a change to fix a problem with appdomains and
statics in mixed mode assemblies (I'm hoping I'm remembering correctly), so
you actually need to compile with a special switch (/clr:initialAppDomain,
you can see more details of this here [1] and here [2]).

[1] ms-help://MS.MSDNQTR.2003FEB.1033/vccore/html/vcrefEECOMCompilation.htm
[2] http://support.microsoft.com/default...;en-us;Q309694
[3]
ms-help://MS.MSDNQTR.2003FEB.1033/cpguide/html/cpcontargetingnetframeworkver
sion.htm
--
Tomas Restrepo
to****@mvps.org

[Anthony Gallagher]

Thanks for all your help Tomas.

Anthony

Tomas Restrepo (MVP) wrote:

Hi Anthony,

I see. That makes more sense. Naturally an app made with VS.NET 2003
will not work on a machine with only the 1.0 framework, correct?

Ahh, tricky question! Yes and no. As long as you don't use any v1.1-specific
functionality, you can add a special ssection to your app.config file and
have it run against 1.0. (see [3]) However, for MC++ apps, things are
trickier, since there was a change to fix a problem with appdomains and
statics in mixed mode assemblies (I'm hoping I'm remembering correctly), so
you actually need to compile with a special switch (/clr:initialAppDomain,
you can see more details of this here [1] and here [2]).

[1] ms-help://MS.MSDNQTR.2003FEB.1033/vccore/html/vcrefEECOMCompilation.htm
[2] http://support.microsoft.com/default...;en-us;Q309694
[3]
ms-help://MS.MSDNQTR.2003FEB.1033/cpguide/html/cpcontargetingnetframeworkver
sion.htm