VStudio 2002 using wrong version of .Net

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jesper Stocholm - 08 May 2005 19:53 GMT

I have just installed Windows XP from scratch. Before installing .Net from
Windows-update I installed VStudio 2002 and the installation installed .Net
1.0. I have also installed version 1.1 of the framework, but it seems that
VStudio still uses version 1.0 - at least that is what I conclude from the
fact that I cannot compile classes that use System.Data.Odbc - an inclusion
with 1.1 of the framework.

Can any of you guys figure out what I can do to make VStudio 2002 use .Net
1.1?

Thanks,

:o)

Signature

Jesper Stocholm
http://stocholm.dk

Reply to this Message

Mattias Sjögren - 08 May 2005 21:12 GMT

Jesper,

>Can any of you guys figure out what I can do to make VStudio 2002 use .Net
>1.1?

You can't. Upgrade to VS2003.

Mattias

Signature

Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

Reply to this Message

jesper.stocholm@gmail.com - 09 May 2005 11:25 GMT

Hi Mattias,

Thanks for your reply ... and 'pardon my French, but you are kidding,
right? I have found a work-around by adding a reference-path to each
project in my current solution. This path points to my 1.1 directory -
but it really is a crappy solution.

I see that you are an MVP, but are you 100% sure there is no "real"
work-around?

Thanks,

Jesper Stocholm
http://stocholm.dk

Reply to this Message

Mattias Sjögren - 09 May 2005 14:55 GMT

>I see that you are an MVP, but are you 100% sure there is no "real"
>work-around?

I don't know what you consider "real". VS2002 will always use the v1.0
compiler, but you can certainly make it reference v1.1 assemblies. And
you can use a config file to make your app run under the v1.1
framework.

But the recommended solution is still to use VS2003 when targeting
v1.1 of the framework.

Mattias

Signature

Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

Reply to this Message

jesper.stocholm@gmail.com - 09 May 2005 17:38 GMT

Hi Mattias,

Thanks for your reply. Do you know if VStudio 2003 has the same problem
- so that I cannot update the compiler for version 2.0 of .Net when it
arrives? I am a bit reluctant to upgrade to 2003 if I will get into the
same mess again when .Net 2.0 arrives.

Thanks,

Jesper Stocholm
http://stocholm.dk

Reply to this Message

Mattias Sjögren - 09 May 2005 21:10 GMT

>Thanks for your reply. Do you know if VStudio 2003 has the same problem
>- so that I cannot update the compiler for version 2.0 of .Net when it
>arrives?

Yes, even more so than the previous upgrade. There have been some file
format changes in 2.0 so you will most likely not be able to reference
framework 2.0 assemblies from VS2003.

>I am a bit reluctant to upgrade to 2003 if I will get into the
>same mess again when .Net 2.0 arrives.

Well VS2005 will not compile for v1.1 of the framework either, only
v2.0 (at least that's the only supported target version). So you'll
have to ask yourself how important it is to target v1.1.

Of course you can use a build tool other than VS and just invoke the
appropriate command line compiler version.

Mattias

Signature

Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

Reply to this Message

VStudio 2002 using wrong version of .Net

Free Magazines