Framework 2.0 and VS.NET 2003

[Guest]

Hi

I would like to know the compatibility of .NET Framework 2.0 and VS.NET
2003. Will everything work fine in this combination?
What might be the framework factors, which would not be available, as we are
using a 2003 IDE version?

Need your help in this

Prem

 

[pvdg42]

Hi

I would like to know the compatibility of .NET Framework 2.0 and VS.NET
2003. Will everything work fine in this combination?
What might be the framework factors, which would not be available, as we
are
using a 2003 IDE version?

Need your help in this

Prem

Visual Studio .NET 2003 works with .NET Framework v1.1. To use .NET
Framework v2.0, you need Visual Studio 2005.

 

[Cowboy \(Gregory A. Beamer\)]

You can compile in 2003 and stick on a .NET 2.0 server without problems most
of the time (it is unusual you will hit one of the few hotspots, as the
focus for 2.0 was backward compatibility). You cannot, however, compile for
2.0.

The best solution is code and test in 1.1 and then create a script to
compile the project using the 2.0 command line compiler. There are some
optimizations in the 2.0 compiler(s) that will be of benefit.

You also have the option of using the Express products, but cannot compile
multiple project solutions, so you end up compiling libraries and apps
separately.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************************************************
Think outside of the box!
*************************************************

 

[keremskusmezer]

Use SharpDevelop 2.0. It is free and allows you in the same IDE , to
compile to .Net 1.0 , 1.1 , 2.0 And Mono. Whole in the same IDE, i
think it really sucks on VS.Net 2005 that you can only compile to 2.0,
instead of compiling to 1.0 , 1.1 , 2.0. If you need such an support
like always you have to pay $$$ s to the Micro$oft.