Diego Gonzalez

.NET, movies & //TODO:

Converting a VS.NET project from 2002 to 2003

Have you check the differences between the SLN and the CSPROJ files between VS2002 y VS2003? It's incredible i've been checking the files and i find an UNSUPPORTED way to convert the project files so you can open the solution with any VS version. On the .sln file you will get the following text on VS.NET 2003: 
Microsoft Visual Studio Solution File, Format Version 8.00
But in VS.NET 2002 the version is 7.00... very funny. On the CSPROJ file which is an XML file, you will fine the following node: 
    <CSHARP
        ProjectType = "Local"
        ProductVersion = "7.10.3077"
        SchemaVersion = "2.0"
        ProjectGuid = "{4B2C7E90-EE53-4887-8C5E-2F57F414E305}"
    >
If you change the "SchemaVersion" attribute to "1.0" and the "ProductVersion" to "7.0.9466" this file can be readed with VS.NET 2002, you may get some warnings but it works... I have some questions about this? Why VS.NET team does not use XML to define the SLN files? If the schemas gets public it will be great for external tools to generate every solution file, i mean the SLN, CSPROJ, XSX, etc.

Silly solutions for a silly world.
Posted: Aug 07 2003, 04:28 PM by DiegoGonzalez | with 4 comment(s)
Filed under:

Comments

Jesse Ezell said:

There is a utility on CodeProject to do all the conversions for you.
# August 7, 2003 2:42 PM

Stephane Rodriguez said:


>> the schemas gets public it will be great for external tools to generate every solution file, i mean the SLN, CSPROJ, XSX, etc.

- CodeProject.com has backward converters so you don't have to worry about it. 2003==>2002 (C++,C#) and 2002==>6.0 (C++)

- VS.NET is too broad a term. You've got to differentiate between VC++.NET, VC#.NET cause the schemas are not the same.

- it's MS business to push upgrades, so they broke the file formats just as well as they did between VC++6.0 and VC++.NET 2002. And guess what, VC++.NET 2004 will probably change the file formats again. Who knows?

- "the schemas get public" : it's MS strategy to take away open xml documents and make them as proprietary as binary stuff by having a private schema that they can change over time, whenever they want, and by the way they force developers to adapt along the way or...die. Yes, closedness of xml namespaces is key to web services, office 2003 interoperability, sql xml queries, .... A lot of things in fact.
# August 7, 2003 3:55 PM

ajaya agarwal said:

its really helps to open projects of VS.NET 2003 in vs.net2002 .

Thanks
ajaya
# April 19, 2004 2:28 AM

Mach said:

Thanks for the tip, man. Really great.
It works for VB almost seamlessly.
# July 10, 2004 10:25 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)