just installed 1.1 - now how do i use it?! =)

[K. Shier]

i have a VB.Net project that i began authoring under framework v1.0

i just installed 1.1* and now would like to start accessing the added
functionality of it, but whenever i check my references, they all still
point to 1.0 dlls.

i think i can handle manually re-setting the references to the 1.1 dlls but
is there an easier/automatic way to handle this?

is there some configuration setting to tell VS.Net to 'Use Framework Version
____'?

are there any dangers in upgrading to 1.1 in the middle of a project?

any insight would be much appreciated! THANKS! =)

 

[Mattias Sjögren]

is there some configuration setting to tell VS.Net to 'Use Framework Version
____'?

Not VS.NET 2002, no. It only works with v1.0 of the framework. You
should upgrade to VS.NET 2003 to target v1.1.



Mattias

 

[K. Shier]

ouch! so there is _no way_ to use v1.1 methods in a project being designed
in VS.Net 2002?

my first impulse was to say "that's odd!", but when i consider the fact that
it forces all the 2002 users to upgrade (and consider who is the 'forced
distribution' mastermind behind this all), it doesn't seem odd at all... =|

don't people who aren't using VS.Net have the ability to target whichever FW
version they want? if so, how? (not that i am going to switch to
developing in Notepad, but i am just curious...)

thanks for the reply, Mattias!

 

[Mattias Sjögren]

my first impulse was to say "that's odd!", but when i consider the fact that
it forces all the 2002 users to upgrade (and consider who is the 'forced
distribution' mastermind behind this all), it doesn't seem odd at all... =|

don't people who aren't using VS.Net have the ability to target whichever FW
version they want? if so, how? (not that i am going to switch to
developing in Notepad, but i am just curious...)

Well, you can use VS.NET 2002 just for coding and debugging, and then
compile with the v1.1 command line compilers.



Mattias

 

[Jay B. Harlow [MVP - Outlook]]

K. Shier,
In addition to Mattias's comments.

Today is the last day for the $29 (U.S.) upgrade to VS.NET 2003.

http://msdn.microsoft.com/vstudio/howtobuy/upgrade/vstudio03/default.aspx

The upgrade has a number of IDE fixes in it in addition to support for .NET
1.1.

Hope this helps
Jay

ouch! so there is _no way_ to use v1.1 methods in a project being designed
in VS.Net 2002?

my first impulse was to say "that's odd!", but when i consider the fact that
it forces all the 2002 users to upgrade (and consider who is the 'forced
distribution' mastermind behind this all), it doesn't seem odd at all... =|

don't people who aren't using VS.Net have the ability to target whichever FW
version they want? if so, how? (not that i am going to switch to
developing in Notepad, but i am just curious...)

thanks for the reply, Mattias!

 

[Jay B. Harlow [MVP - Outlook]]

K. Shier,
In addition to Mattias's comments.

Today is the last day for the $29 (U.S.) upgrade to VS.NET 2003.

http://msdn.microsoft.com/vstudio/howtobuy/upgrade/vstudio03/default.aspx

The upgrade has a number of IDE fixes in it in addition to support for .NET
1.1.

Hope this helps
Jay

ouch! so there is _no way_ to use v1.1 methods in a project being designed
in VS.Net 2002?

my first impulse was to say "that's odd!", but when i consider the fact that
it forces all the 2002 users to upgrade (and consider who is the 'forced
distribution' mastermind behind this all), it doesn't seem odd at all... =|

don't people who aren't using VS.Net have the ability to target whichever FW
version they want? if so, how? (not that i am going to switch to
developing in Notepad, but i am just curious...)

thanks for the reply, Mattias!

 

[K. Shier]

to my dismay, i learned about this on the morning of October 1... thanks
anyway, though!

the main reason i wanted 1.1 is because i thought they either added or
restructured some things in System.Runtime.Remoting - an online code example
i wanted to work off of wouldn't compile under 1.0 framework. but i found
another solution to the base issue, so 1.1 is non-essential at the moment.

new IDE would have been fun, though...