VB.Net, VS.Net Version vs .Net Framework version

VS.Net Version vs .Net Framework version

Author	Message
Chris Dunawa #1 / 20	VS.Net Version vs .Net Framework version I have seen several posts asking about certain features in the framework and the response has been something to the effect of: "Yeah, that's a new feature in the 1.1 framework, but you can only access it using VS.Net 2003" This begs the question: The .Net Framework and VS.Net are essentially different things. It is quite likely that the Framework may get patches, bug fixes, etc. at a different rate than VS.Net. It seems quite logical, then, that if a new version of the framework is released, that the current version of VS.Net ought to be able to target it. And if more changes to the framework are made, the current version of VS.Net should be able to target it. Even if the framework changes 1000 times before VS.Net has any changes, I would expect VS.Net to be able to take advantage of those changes. Is this not so? Case in point: The 1.1 framework adds a method "UseVisualStyles" to the Application object. Why must I get VS.Net 2003 in order to use that method? Should not VS.Net 2002 be able to use any version of the framework that is present on the machine? And if so, shouldn't it be able to access the Application.UseVisualStyles method? Just trying to understand how changes to the Framework will affect VS.Net. Chris -- If you don't like lunchmeat, please remove it from my e-mail address to send me an e-mail
Wed, 06 Jul 2005 03:01:24 GMT

Lino Barrec #2 / 20	VS.Net Version vs .Net Framework version You can use framework 1.1 with vs 2002. When you make a new project you must change the references in your project to point to .net 1.1 assemblies. In this way VS 2002 uses the 1.1 instead of 1.0. Note: You should avoid using 1.1 until it's in beta testing phase. If you compile an app (and distribute it) that uses 1.1beta probably it will not work with the definitive 1.1 framework. If I remember the app tries to load the assembly of the same version you used at build time and if it can't find the same "major.minor.build" it should load a precedent assembly version. So the app will not work. Quote: > I have seen several posts asking about certain features in the framework > and the response has been something to the effect of: "Yeah, that's a new > feature in the 1.1 framework, but you can only access it using VS.Net 2003" > This begs the question: > The .Net Framework and VS.Net are essentially different things. It is > quite likely that the Framework may get patches, bug fixes, etc. at a > different rate than VS.Net. It seems quite logical, then, that if a new > version of the framework is released, that the current version of VS.Net > ought to be able to target it. And if more changes to the framework are > made, the current version of VS.Net should be able to target it. > Even if the framework changes 1000 times before VS.Net has any changes, I > would expect VS.Net to be able to take advantage of those changes. Is this > not so? > Case in point: The 1.1 framework adds a method "UseVisualStyles" to the > Application object. Why must I get VS.Net 2003 in order to use that > method? Should not VS.Net 2002 be able to use any version of the framework > that is present on the machine? And if so, shouldn't it be able to access > the Application.UseVisualStyles method? > Just trying to understand how changes to the Framework will affect VS.Net. > Chris > -- > If you don't like lunchmeat, please remove it from my e-mail address to > send me an e-mail
Wed, 06 Jul 2005 14:49:37 GMT

Nick #3 / 20	VS.Net Version vs .Net Framework version Well that's excellent to hear, I was beginning to think the same thing. I was a little confused how Microsoft seemed to have poured loads into trying to get people to migrate to .NET and now when I purchased Visual Basic.NET 2002 I was under the impression that I would be forced to upgrade to yet a newer version, to be able to support the new framework. Oh well, thanks for clarifying this for me also. Nick. Quote: > You can use framework 1.1 with vs 2002. > When you make a new project you must change the references in your project > to point to .net 1.1 assemblies. > In this way VS 2002 uses the 1.1 instead of 1.0. > Note: You should avoid using 1.1 until it's in beta testing phase. > If you compile an app (and distribute it) that uses 1.1beta probably it will > not work with the definitive 1.1 framework. > If I remember the app tries to load the assembly of the same version you > used at build time and if it can't find the same "major.minor.build" it > should load a precedent assembly version. > So the app will not work. messaggio > > I have seen several posts asking about certain features in the framework > > and the response has been something to the effect of: "Yeah, that's a new > > feature in the 1.1 framework, but you can only access it using VS.Net > 2003" > > This begs the question: > > The .Net Framework and VS.Net are essentially different things. It is > > quite likely that the Framework may get patches, bug fixes, etc. at a > > different rate than VS.Net. It seems quite logical, then, that if a new > > version of the framework is released, that the current version of VS.Net > > ought to be able to target it. And if more changes to the framework are > > made, the current version of VS.Net should be able to target it. > > Even if the framework changes 1000 times before VS.Net has any changes, I > > would expect VS.Net to be able to take advantage of those changes. Is > this > > not so? > > Case in point: The 1.1 framework adds a method "UseVisualStyles" to the > > Application object. Why must I get VS.Net 2003 in order to use that > > method? Should not VS.Net 2002 be able to use any version of the > framework > > that is present on the machine? And if so, shouldn't it be able to access > > the Application.UseVisualStyles method? > > Just trying to understand how changes to the Framework will affect VS.Net. > > Chris > > -- > > If you don't like lunchmeat, please remove it from my e-mail address to > > send me an e-mail
Wed, 06 Jul 2005 23:03:35 GMT

jame #4 / 20	VS.Net Version vs .Net Framework version Visual Studio.NET 2002 is locked to ver.1.0 of the Framework. The only way to make it work with ver. 1.1 is to get rid of ver. 1.0 of the Framework and make some other changes. And not all the features available in ver. 1.1 work correctly with VS.NET 2002. Microsoft has stated that they will offer an upgrade to current users of VS.NET 2002 for $29.00. And both versions work just fine side by side. (I'm using Beta 2 of VS.NET 2003 and VS.NET 2002 now , with no trouble) I too wish they would make it where you only had to go into an Options Menu and change a reference to that latest Framework. But, for now, they haven't. The announced release timeframe is this April for VS.NET 2003. james Quote: > Well that's excellent to hear, I was beginning to think the same thing. I > was a little confused how Microsoft seemed to have poured loads into trying > to get people to migrate to .NET and now when I purchased Visual Basic.NET > 2002 I was under the impression that I would be forced to upgrade to yet a > newer version, to be able to support the new framework. Oh well, thanks for > clarifying this for me also. > Nick. > > You can use framework 1.1 with vs 2002. > > When you make a new project you must change the references in your project > > to point to .net 1.1 assemblies. > > In this way VS 2002 uses the 1.1 instead of 1.0. > > Note: You should avoid using 1.1 until it's in beta testing phase. > > If you compile an app (and distribute it) that uses 1.1beta probably it > will > > not work with the definitive 1.1 framework. > > If I remember the app tries to load the assembly of the same version you > > used at build time and if it can't find the same "major.minor.build" it > > should load a precedent assembly version. > > So the app will not work. > messaggio > > > I have seen several posts asking about certain features in the framework > > > and the response has been something to the effect of: "Yeah, that's a > new > > > feature in the 1.1 framework, but you can only access it using VS.Net > > 2003" > > > This begs the question: > > > The .Net Framework and VS.Net are essentially different things. It is > > > quite likely that the Framework may get patches, bug fixes, etc. at a > > > different rate than VS.Net. It seems quite logical, then, that if a new > > > version of the framework is released, that the current version of VS.Net > > > ought to be able to target it. And if more changes to the framework are > > > made, the current version of VS.Net should be able to target it. > > > Even if the framework changes 1000 times before VS.Net has any changes, > I > > > would expect VS.Net to be able to take advantage of those changes. Is > > this > > > not so? > > > Case in point: The 1.1 framework adds a method "UseVisualStyles" to the > > > Application object. Why must I get VS.Net 2003 in order to use that > > > method? Should not VS.Net 2002 be able to use any version of the > > framework > > > that is present on the machine? And if so, shouldn't it be able to > access > > > the Application.UseVisualStyles method? > > > Just trying to understand how changes to the Framework will affect > VS.Net. > > > Chris > > > -- > > > If you don't like lunchmeat, please remove it from my e-mail address to > > > send me an e-mail
Thu, 07 Jul 2005 00:13:01 GMT

Bruce L- #5 / 20	VS.Net Version vs .Net Framework version Lino, you say this with such great assurance. Have you actually done this? I have seen many, many messages including from MS that what you are stating here is just not true. VS 2002 does NOT support 1.1, not from all I heard. Please be sure before you answer so definitively. You had someone thinking he was in good shape(hopefully he continued to follow the thread and knows differently now). Bruce L-C Quote: > You can use framework 1.1 with vs 2002. > When you make a new project you must change the references in your project > to point to .net 1.1 assemblies. > In this way VS 2002 uses the 1.1 instead of 1.0. > Note: You should avoid using 1.1 until it's in beta testing phase. > If you compile an app (and distribute it) that uses 1.1beta probably it will > not work with the definitive 1.1 framework. > If I remember the app tries to load the assembly of the same version you > used at build time and if it can't find the same "major.minor.build" it > should load a precedent assembly version. > So the app will not work. messaggio > > I have seen several posts asking about certain features in the framework > > and the response has been something to the effect of: "Yeah, that's a new > > feature in the 1.1 framework, but you can only access it using VS.Net > 2003" > > This begs the question: > > The .Net Framework and VS.Net are essentially different things. It is > > quite likely that the Framework may get patches, bug fixes, etc. at a > > different rate than VS.Net. It seems quite logical, then, that if a new > > version of the framework is released, that the current version of VS.Net > > ought to be able to target it. And if more changes to the framework are > > made, the current version of VS.Net should be able to target it. > > Even if the framework changes 1000 times before VS.Net has any changes, I > > would expect VS.Net to be able to take advantage of those changes. Is > this > > not so? > > Case in point: The 1.1 framework adds a method "UseVisualStyles" to the > > Application object. Why must I get VS.Net 2003 in order to use that > > method? Should not VS.Net 2002 be able to use any version of the > framework > > that is present on the machine? And if so, shouldn't it be able to access > > the Application.UseVisualStyles method? > > Just trying to understand how changes to the Framework will affect VS.Net. > > Chris > > -- > > If you don't like lunchmeat, please remove it from my e-mail address to > > send me an e-mail
Fri, 08 Jul 2005 04:40:47 GMT

Nick #6 / 20	VS.Net Version vs .Net Framework version Unfortunatly I have been following the thread and have sworn and cursed greatly. But one thing I wouldn't mind knowing is if the $29 for the new version statement is true, and how would I go about doing that and when is the new version due for release? Nick. Quote: > Lino, you say this with such great assurance. Have you actually done this? I > have seen many, many messages including from MS that what you are stating > here is just not true. VS 2002 does NOT support 1.1, not from all I heard. > Please be sure before you answer so definitively. You had someone thinking > he was in good shape(hopefully he continued to follow the thread and knows > differently now). > Bruce L-C > > You can use framework 1.1 with vs 2002. > > When you make a new project you must change the references in your project > > to point to .net 1.1 assemblies. > > In this way VS 2002 uses the 1.1 instead of 1.0. > > Note: You should avoid using 1.1 until it's in beta testing phase. > > If you compile an app (and distribute it) that uses 1.1beta probably it > will > > not work with the definitive 1.1 framework. > > If I remember the app tries to load the assembly of the same version you > > used at build time and if it can't find the same "major.minor.build" it > > should load a precedent assembly version. > > So the app will not work. > messaggio > > > I have seen several posts asking about certain features in the framework > > > and the response has been something to the effect of: "Yeah, that's a > new > > > feature in the 1.1 framework, but you can only access it using VS.Net > > 2003" > > > This begs the question: > > > The .Net Framework and VS.Net are essentially different things. It is > > > quite likely that the Framework may get patches, bug fixes, etc. at a > > > different rate than VS.Net. It seems quite logical, then, that if a new > > > version of the framework is released, that the current version of VS.Net > > > ought to be able to target it. And if more changes to the framework are > > > made, the current version of VS.Net should be able to target it. > > > Even if the framework changes 1000 times before VS.Net has any changes, > I > > > would expect VS.Net to be able to take advantage of those changes. Is > > this > > > not so? > > > Case in point: The 1.1 framework adds a method "UseVisualStyles" to the > > > Application object. Why must I get VS.Net 2003 in order to use that > > > method? Should not VS.Net 2002 be able to use any version of the > > framework > > > that is present on the machine? And if so, shouldn't it be able to > access > > > the Application.UseVisualStyles method? > > > Just trying to understand how changes to the Framework will affect > VS.Net. > > > Chris > > > -- > > > If you don't like lunchmeat, please remove it from my e-mail address to > > > send me an e-mail
Fri, 08 Jul 2005 06:00:59 GMT

Lino Barrec #7 / 20	VS.Net Version vs .Net Framework version I'm sure the 1.1 framework goes almost ok with 2002. I tried it. When you create a new project it starts with 1.0 by default but you can change it. However you can't use some new features of the new framework/compiler (like vb bit shift operators) with "VS2002 doesn't support 1.1" probably they mean "you can use it but you should not because it is not fully supported." Bye, Lino :) Quote: > Lino, you say this with such great assurance. Have you actually done this? I > have seen many, many messages including from MS that what you are stating > here is just not true. VS 2002 does NOT support 1.1, not from all I heard. > Please be sure before you answer so definitively. You had someone thinking > he was in good shape(hopefully he continued to follow the thread and knows > differently now). > Bruce L-C > > You can use framework 1.1 with vs 2002. > > When you make a new project you must change the references in your project > > to point to .net 1.1 assemblies. > > In this way VS 2002 uses the 1.1 instead of 1.0. > > Note: You should avoid using 1.1 until it's in beta testing phase. > > If you compile an app (and distribute it) that uses 1.1beta probably it > will > > not work with the definitive 1.1 framework. > > If I remember the app tries to load the assembly of the same version you > > used at build time and if it can't find the same "major.minor.build" it > > should load a precedent assembly version. > > So the app will not work. > messaggio > > > I have seen several posts asking about certain features in the framework > > > and the response has been something to the effect of: "Yeah, that's a > new > > > feature in the 1.1 framework, but you can only access it using VS.Net > > 2003" > > > This begs the question: > > > The .Net Framework and VS.Net are essentially different things. It is > > > quite likely that the Framework may get patches, bug fixes, etc. at a > > > different rate than VS.Net. It seems quite logical, then, that if a new > > > version of the framework is released, that the current version of VS.Net > > > ought to be able to target it. And if more changes to the framework are > > > made, the current version of VS.Net should be able to target it. > > > Even if the framework changes 1000 times before VS.Net has any changes, > I > > > would expect VS.Net to be able to take advantage of those changes. Is > > this > > > not so? > > > Case in point: The 1.1 framework adds a method "UseVisualStyles" to the > > > Application object. Why must I get VS.Net 2003 in order to use that > > > method? Should not VS.Net 2002 be able to use any version of the > > framework > > > that is present on the machine? And if so, shouldn't it be able to > access > > > the Application.UseVisualStyles method? > > > Just trying to understand how changes to the Framework will affect > VS.Net. > > > Chris > > > -- > > > If you don't like lunchmeat, please remove it from my e-mail address to > > > send me an e-mail
Fri, 08 Jul 2005 15:20:13 GMT

Criru #8 / 20	VS.Net Version vs .Net Framework version How can I change what Framework version a aplication should point at? Quote: > I have seen several posts asking about certain features in the framework > and the response has been something to the effect of: "Yeah, that's a new > feature in the 1.1 framework, but you can only access it using VS.Net 2003" > This begs the question: > The .Net Framework and VS.Net are essentially different things. It is > quite likely that the Framework may get patches, bug fixes, etc. at a > different rate than VS.Net. It seems quite logical, then, that if a new > version of the framework is released, that the current version of VS.Net > ought to be able to target it. And if more changes to the framework are > made, the current version of VS.Net should be able to target it. > Even if the framework changes 1000 times before VS.Net has any changes, I > would expect VS.Net to be able to take advantage of those changes. Is this > not so? > Case in point: The 1.1 framework adds a method "UseVisualStyles" to the > Application object. Why must I get VS.Net 2003 in order to use that > method? Should not VS.Net 2002 be able to use any version of the framework > that is present on the machine? And if so, shouldn't it be able to access > the Application.UseVisualStyles method? > Just trying to understand how changes to the Framework will affect VS.Net. > Chris > -- > If you don't like lunchmeat, please remove it from my e-mail address to > send me an e-mail
Fri, 08 Jul 2005 17:41:30 GMT

Mark Pearc #9 / 20	VS.Net Version vs .Net Framework version Hi Crirus, See this Visual Studio Magazine article http://tinyurl.com/4ngk Hope this helps, Mark How can I change what Framework version a aplication should point at? Quote: > I have seen several posts asking about certain features in the framework > and the response has been something to the effect of: "Yeah, that's a new > feature in the 1.1 framework, but you can only access it using VS.Net 2003" > This begs the question: > The .Net Framework and VS.Net are essentially different things. It is > quite likely that the Framework may get patches, bug fixes, etc. at a > different rate than VS.Net. It seems quite logical, then, that if a new > version of the framework is released, that the current version of VS.Net > ought to be able to target it. And if more changes to the framework are > made, the current version of VS.Net should be able to target it. > Even if the framework changes 1000 times before VS.Net has any changes, I > would expect VS.Net to be able to take advantage of those changes. Is this > not so? > Case in point: The 1.1 framework adds a method "UseVisualStyles" to the > Application object. Why must I get VS.Net 2003 in order to use that > method? Should not VS.Net 2002 be able to use any version of the framework > that is present on the machine? And if so, shouldn't it be able to access > the Application.UseVisualStyles method? > Just trying to understand how changes to the Framework will affect VS.Net. > Chris > -- > If you don't like lunchmeat, please remove it from my e-mail address to > send me an e-mail
Fri, 08 Jul 2005 20:29:55 GMT

Chris Dunawa #10 / 20	VS.Net Version vs .Net Framework version Quote: > side. (I'm using Beta 2 of VS.NET 2003 and VS.NET 2002 now , with no > trouble) I too wish they would make it where you only had to go into I, too, have the beta of VS.Net 2003. My question concerned updates to the framework. I shouldn't have to upgrade my version of VS.Net in order to use the new framework. VS.Net may be locked to 1.0, but I hope future versions will allow me to choose the framework that I wish to target. Chris -- If you don't like lunchmeat, please remove it from my e-mail address to send me an e-mail
Sat, 09 Jul 2005 02:08:06 GMT

Chris Dunawa #11 / 20	VS.Net Version vs .Net Framework version Quote: > However you can't use some new features of the new framework/compiler > (like vb bit shift operators) This makes no sense to me. Isn't VS.Net just calling the compiler that ships with the framework? If that compiler supports the new features, then VS.Net should support them. -- If you don't like lunchmeat, please remove it from my e-mail address to send me an e-mail
Sat, 09 Jul 2005 02:10:12 GMT

Chris Dunawa #12 / 20	VS.Net Version vs .Net Framework version This topic was posted out of a discussion of the Application.EnableVisualStyles property. This property is not available in 1.0 of the framework. My question concerned VS.Net 2002 and updates to the framework. My contention is that I should not have to upgrade my version of VS.Net in order to use new features of the framework. I understand that I will not be able to use new features of VS.Net 2003 unless I upgrade, but new features in the FRAMEWORK should be available to me in VS.Net 2002. I experimented with the devenv.exe.config file for VS.Net 2002 and found that if I updated the version numbers in that file, that my projects would now reference the 1.1 framework and the EnableVisualStyles property is available in VS.Net 2002. My next question is this: Is it safe to modify that file? How can I tell VS.Net 2002 to "point at" the 1.1 framework? Chris -- If you don't like lunchmeat, please remove it from my e-mail address to send me an e-mail
Sat, 09 Jul 2005 02:44:50 GMT

Chris Dunawa #13 / 20	VS.Net Version vs .Net Framework version Quote: > the Framework and make some other changes. And not all the features > available in ver. 1.1 work correctly with VS.NET 2002. This confuses me also. I would expect that new features of VS.Net 2003 to be missing from VS.Net 2002, but if I install an updated version of the Framework, I should be able to access all of it's features from VS.Net 2002. Is this not so? Is there a MS person who could shed some light on this subject? Chris -- If you don't like lunchmeat, please remove it from my e-mail address to send me an e-mail
Sat, 09 Jul 2005 02:47:06 GMT

Chris Dunawa #14 / 20	VS.Net Version vs .Net Framework version Quote: > You can use framework 1.1 with vs 2002. > When you make a new project you must change the references in your > project to point to .net 1.1 assemblies. How do you do this? Quote: > Note: You should avoid using 1.1 until it's in beta testing phase. I thought that version 1.1 of the Framework has been officially released? Chris -- If you don't like lunchmeat, please remove it from my e-mail address to send me an e-mail
Sat, 09 Jul 2005 02:48:42 GMT

Nick #15 / 20	VS.Net Version vs .Net Framework version This is getting confusing, can you or can you not use the 1.1 framework with VS.NET 2002? If not, why the hell not!, I thought VB etc, was simply a text editor with flashy features to make it easier to program an application, where the old VB6 etc would use the VB runtime libraries, VB.NET apps use the framework, VB6 apps could use newer runtimes why the hell cant VB.NET use newer frameworks? I smell money, even if it is $29, which I very much doubt!! Nick. Quote: > This topic was posted out of a discussion of the > Application.EnableVisualStyles property. This property is not available in > 1.0 of the framework. My question concerned VS.Net 2002 and updates to the > framework. My contention is that I should not have to upgrade my version > of VS.Net in order to use new features of the framework. I understand that > I will not be able to use new features of VS.Net 2003 unless I upgrade, but > new features in the FRAMEWORK should be available to me in VS.Net 2002. > I experimented with the devenv.exe.config file for VS.Net 2002 and found > that if I updated the version numbers in that file, that my projects would > now reference the 1.1 framework and the EnableVisualStyles property is > available in VS.Net 2002. > My next question is this: Is it safe to modify that file? How can I tell > VS.Net 2002 to "point at" the 1.1 framework? > Chris > -- > If you don't like lunchmeat, please remove it from my e-mail address to > send me an e-mail
Sat, 09 Jul 2005 06:46:56 GMT

Page 1 of 2

[ 20 post ]

Go to page: [1] [2]