retro conversion to VS2003

[OSI Mik]

Hello,
I take a project which is in production with a Visual studio 2003 version
(Visual C++)
When i open source un visual C++ 2003, I have a notification that the source
is in a newer version.
Indeed, in the file sln :
Microsoft Visual Studio Solution File, Format Version 9.00
# Visual C# Express 2005

How could I know the real version of the source ? (C++ / C# and 2003 / 2005
/ 2008)
How could I make a retro conversion of source to 2003 ?
If we put the current version (2005 / 2008) in production, are there some
risk ?
I also need documentation on automatique conversion of source code.
Thank's for your help,
Osi Mik

 

[DeveloperX]

Hello,
I take a project which is in production with a Visual studio 2003 version
(Visual C++)
When i open source un visual C++ 2003, I have a notification that the source
is in a newer version.
Indeed, in the file sln :
    Microsoft Visual Studio Solution File, Format Version 9.00
    # Visual C# Express 2005

How could I know the real version of the source ? (C++ / C# and 2003 / 2005
/ 2008)
How could I make a retro conversion of source to 2003 ?
If we put the current version (2005 / 2008) in production, are there some
risk ?
I also need documentation on automatique conversion of source code.
Thank's for your help,
Osi Mik

The biggest potential problem here is they've used framework 2+
features like generics which aren't supported in 2003 (1.1). If that's
the case you'll have to rewrite significant portions although it's not
really that hard, just time consuming.

I know of no way to convert the sln or proj files backwards, but as
you noted they are just text files.

The easiest way to do it is create a new sln with new project(s) and
manually add the old .cs files and copy and paste in the references to
the proj files. If it compiles, cool, but if doesn't you've got a bit
of work ahead. The worst case is it's a forms app or web app which
could use controls not available in 1.1. for forms that can be quite
bad, but asp.net 2 is really really different to 1.1 and probably
isn't worth the hassle.

Finally, remember Express is free to download, so you could get the
latest version open the project in that and it will give you the
opportunity to see whether you're missing references, what language is
in use, what features are used, etc. The various versions sit side by
side very happily.

 

[christery]

Hello,
Might point out that there is a bit to do if converting c# to c++ or
vice versa
like converting to fortran, pascal, vb... that it understands the sln
flie indicates vs2003 not just c++ but what do I know...

//CY

 

[OSI Mik]

I will try this, with 2 machine with differente version.
Thank you for this information.
Osi Mik

"DeveloperX" <[email protected]> a écrit dans le message de
news: (e-mail address removed)...

Hello,
I take a project which is in production with a Visual studio 2003 version
(Visual C++)
When i open source un visual C++ 2003, I have a notification that the
source
is in a newer version.
Indeed, in the file sln :
Microsoft Visual Studio Solution File, Format Version 9.00
# Visual C# Express 2005

How could I know the real version of the source ? (C++ / C# and 2003 /
2005
/ 2008)
How could I make a retro conversion of source to 2003 ?
If we put the current version (2005 / 2008) in production, are there some
risk ?
I also need documentation on automatique conversion of source code.
Thank's for your help,
Osi Mik

The biggest potential problem here is they've used framework 2+
features like generics which aren't supported in 2003 (1.1). If that's
the case you'll have to rewrite significant portions although it's not
really that hard, just time consuming.

I know of no way to convert the sln or proj files backwards, but as
you noted they are just text files.

The easiest way to do it is create a new sln with new project(s) and
manually add the old .cs files and copy and paste in the references to
the proj files. If it compiles, cool, but if doesn't you've got a bit
of work ahead. The worst case is it's a forms app or web app which
could use controls not available in 1.1. for forms that can be quite
bad, but asp.net 2 is really really different to 1.1 and probably
isn't worth the hassle.

Finally, remember Express is free to download, so you could get the
latest version open the project in that and it will give you the
opportunity to see whether you're missing references, what language is
in use, what features are used, etc. The various versions sit side by
side very happily.