INFO: Why Visual Studio targets only one version of the .NET Framework

[Carlos J. Quintero [VB MVP]]

Hi,

This is a question that is asked quite often, so here is some recent info
from insde Microsoft:

Why Visual Studio targets only one version of the .NET Framework
http://blogs.msdn.com/johnri/archive/2005/11/29/498219.aspx

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

 

[narzis]

I cannot understand I write Win32 Application still, but cannot write
..NET 1.1 Application.

Carlos J. Quintero [VB MVP] 작성:

 

[m.posseth]

I just discovered the following

i am currently bussy with a new project ( going to be released in march
2006 ) however it is written in VS 2003 and uses Cassini , sharpziblib
library , a webservice and remoting interface
( pretty complicated project )

well i started my beta version on a computer with only the .Net 2.0
framework installed and it worked perfectly !!

So i am now starting to upgrade my sourcecode , as this would mean that i
will only have to ship the 2.0 framework with my app and it will give me all
the benefits of the 2005 IDE


regards

Michel Posseth [MCP]

 

[Larry Lard]

Hi,

This is a question that is asked quite often, so here is some recent info
from insde Microsoft:

Why Visual Studio targets only one version of the .NET Framework
http://blogs.msdn.com/johnri/archive/2005/11/29/498219.aspx

So, the reason it's too hard to make VS target multiple frameworks, is
because a particular VS is tightly integrated with a particular
framework. OK.

But when VS 7 was being made - *from scratch* - did no one think, hmm,
there's going to be a new framework version at some point, maybe we
shouldn't tightly couple to 1.0? Did they think framework 1.0 was going
to last for ever?

(from that article)

I strongly support the initiative for a toolset that can target
multiple versions of the Microsoft Windows and CLR platforms.

.... so why didn't you make one in the first place, when you had a blank
piece of paper and nothing to be backward compatible with??

 

[Carlos J. Quintero [VB MVP]]

I agree, but I suppose that VS.NET 7.0 was version 1.0 of a huge new product
using a new technology and backwards compatibility was not a priority. Also,
much of the versioning problems don´t become apparent until you have a 2nd
version, and MS is learning about it through all these years and adjusting
the .NET Framework accordingly with new classes and methods. The good news
is that top management (Corporate Vice President, Developer Division) are
willing to go there:

Multi-targeting of .NET FX in Visual Studio
http://blogs.msdn.com/somasegar/archive/2005/11/30/498288.aspx


--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

 

[Carlos J. Quintero [VB MVP]]

<[email protected]> escribió en el mensaje
I cannot understand I write Win32 Application still, but cannot write
..NET 1.1 Application.

Because of the .NET Framework versioning, it is explained in the weblog...

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

 

[Carlos J. Quintero [VB MVP]]

That's great, but we are talking about using VS 2005 to create .NET 1.x
assemblies, which some people would like (including me).

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com