Visual Studio and Framework 2.0 and Framework 1.X

  • Thread starter Thread starter D Redfield
  • Start date Start date
D

D Redfield

We program using Visual Studio and have followed the beta closely and now
its time to install the real thing on real developer workstations. Our
issue is this: About 50 per cent of our c# code in targeted for a system
which does not support 2.0 (at least not until Q1/06). Can any one point me
at a white paper on using VS 2005 and targeting SOME solutions for Framework
1.X and SOME solutions for Framework 2.0?

thanks

dlr
 
You will have to have both VS.NET and VS 2005 installed and edit each
project in its own IDE. You can develop in one and target another, but it
will require compilation in the proper framework and close attention to any
breaking changes:


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

***********************************************
Think Outside the Box!
***********************************************
 
You will have to have both VS.NET and VS 2005 installed and edit each
project in its own IDE. You can develop in one and target another, but it
will require compilation in the proper framework and close attention to any
breaking changes:
http://msdn.microsoft.com/netframework/programming/breakingchanges/default.aspx

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

***********************************************
Think Outside the Box!
***********************************************
 
I thought we better options. I know that VS2005 has an option to restrict
to v1.X syntax. But you are saying there is no way to get VS2005 to compile
for
Framework 1.X? Seems like a poor option to require two IDE's to be
installed but if that is what it takes, that's what it takes....

dlr
 
Hi

In the source code level, the 1.1 and 2.0 code is compatible to some
extent.
e.g.
The Form.Show code is same for .NET 2.0 and .NET 1.1.
But some component is only in the .NET 2.0 but no .NET 1.1. e.g. the
WebBrowser managed control is only instroduced in .NET 2.0.

Also the solution file in 2.0 will no be opened with 1.1, but 1.1's
solution can be opened in .NET 2.0(it will invoke a convertion dialog).
So for your scenario, I suggest you run the .NET 2.0 code in .NET 2.0 but
not .NET 1.1, otherwise you will have to do many manually adjusts,


Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top