.Net 2002 Vs. .Net 2003

[Larry Pits]

Hi All,

Is there a backward compatability issue regarding to .Net 2002 and .Net
2003? I heard someone said that if you're developing in .Net 2003 and gave
the entire project to someone who is developing using VS .Net 2002 and they
can't open the solution file (.sln). Is there a solution to fix this
problem. TIA

[Kerry Sanders]

>Is there a backward compatability issue regarding to .Net 2002 and .Net

2003? I heard someone said that if you're developing in .Net 2003 and gave
the entire project to someone who is developing using VS .Net 2002 and they
can't open the solution file (.sln). Is there a solution to fix this
problem. TIA

Nope. You can go forward, but not back. When you open a project/solution
developed with .Net 2002 in .Net 2003, it pops up a message notifying of you of
this fact and that you cannot open it again in .Net 2002.

> Is there a backward compatability issue regarding to .Net 2002 and .Net

2003? I heard someone said that if you're developing in .Net 2003 and gave the entire project to someone who is developing using VS .Net 2002 and they can't open the solution file (.sln). Is there a solution to fix this
problem. TIA

You can by opening the configuration files with notepad, and copy the 2002
typical headers to the 2003 project.
*.csproj, *.csproj.user and *.sln I think. (You have to check out the
differences for your application)
And it will be trial and error.

Make sure you have a complete backup of the project since messing around
with controls that have properties in 2003 but suddenly have only properties
of 2002 might mess up your forms. I had this several times.

[Jay B. Harlow [MVP - Outlook]]

Larry,
There is a utility at Code Project that will convert a VS.NET 2003 solution
back to VS.NET 2002.

http://www.codeproject.com/macro/vsconvert.asp

As long as you stay away from VB.NET 2003 constructs (For Each item As
Integer & bit shift operators) there should be no real problems converting
the project back to VS.NET 2002 when working on it on campus.

The one quirk you will find is that VB.NET 2003 removes the parenthesis on
the constructor when creating new objects with the default constructor,
while VB.NET 2002 wants them there.

' VS.NET 2003 syntax
Dim x as New MainForm

' VS.NET 2002 syntax
Dim x as New MainForm()

I don't know of any language changes from C# 1.0 to C# 1.1, but you may have
similar issues there.

Hope this helps
Jay
"Larry Pits" <lp***@hotmail.com> wrote in message
news:eX**************@TK2MSFTNGP12.phx.gbl...

Hi All,

Is there a backward compatability issue regarding to .Net 2002 and .Net
2003? I heard someone said that if you're developing in .Net 2003 and gave the entire project to someone who is developing using VS .Net 2002 and they can't open the solution file (.sln). Is there a solution to fix this
problem. TIA