A Simple way to make VS.NET 2003 prjects back to VS.NET 2002 projects |
| | | | Submitted on: 5/27/2003 5:28:10 AM
By: Unruled Boy
Level: Advanced User Rating:
By 3 Users Compatibility:C#, VB.NET
Users have accessed this article 2658 times. | (About the author) |
| | Because VS.NET 2003 uses a new format (actually some new tags and version identifiers.), we cannot open those projects/solutions that created/modified by VS.NET 2003 with VS.NET 2002. Yet, there is a simple way to solve this problem.
This article has accompanying files | |
|
Terms of Agreement:
By using this article, you agree to the following terms...
1) You may use
this article in your own programs (and may compile it into a program and distribute it in compiled format for languages that allow it) freely and with no charge.
2) You MAY NOT redistribute this article (for example to a web site) without written permission from the original author. Failure to do so is a violation of copyright laws.
3) You may link to this article from another website, but ONLY if it is not wrapped in a frame.
4) You will abide by any additional copyright restrictions which the author may have placed in the article or article's description. | A Simple way to make VS.NET
2003 back to VS.NET 2002
Unruled Boy 2003-5-27
Because
VS.NET 2003 uses a new format (actually some new tags and version identifiers.),
we cannot open those projects/solutions that created/modified by VS.NET 2003
with VS.NET 2002.
Yet, there
is a simple way to solve this problem.
Step
1: Modify the Solution Files
Change
the first line of the solution files from ¡°Microsoft Visual Studio Solution
File, Format Version 8.00¡± to ¡°Microsoft Visual Studio Solution File, Format Version
7.00¡±
Step
2: Modify the Project Files
A.
For C Sharp:
<VisualStudioProject>
<CSHARP
ProjectType = "Local"
ProductVersion = "7.10.3707"
SchemaVersion = "2.0"
ProjectGuid = "{20502969-7071-4065-BDB5-09EDB3C31E3C}"
>
Change the above lines to the following lines:
<VisualStudioProject>
<CSHARP
ProjectType = "Local"
ProductVersion = "7.0.9466"
SchemaVersion = "1.0"
ProjectGuid = "{20502969-7071-4065-BDB5-09EDB3C31E3C}"
>
Beaware of the ProjectGuid, it should be
same with actual ones.
B.
For Visual Basic.NET
<VisualBasic
ProjectType = "Local"
ProductVersion = "7.10.3707"
SchemaVersion = "2.0"
ProjectGuid = "{6E100C4A-A121-4C1F-83BF-BE639BC59CF1}"
>
Change the above lines to the following lines:
<VisualBasic
ProjectType = "Local"
ProductVersion = "7.0.9466"
SchemaVersion = "1.0"
ProjectGuid = "{6E100C4A-A121-4C1F-83BF-BE639BC59CF1}"
>
| |
Download article
Note: Due to the size or complexity of this submission, the author has submitted it as a .zip file to shorten your download time. Afterdownloading it, you will need a program like Winzip to decompress it.
Virus note:All files are scanned once-a-day by Planet Source Code for viruses,but new viruses come out every day, so no prevention program can catch 100% of them.
FOR YOUR OWN SAFETY, PLEASE: 1)Re-scan downloaded files using your personal virus checker before using it. 2)NEVER, EVER run compiled files (.exe's, .ocx's, .dll's etc.)--only run source code.
If you don't have a virus scanner, you can get one at many places on the net including:McAfee.com
|
Terms of Agreement:
By using this article, you agree to the following terms...
1) You may use
this article in your own programs (and may compile it into a program and distribute it in compiled format for languages that allow it) freely and with no charge.
2) You MAY NOT redistribute this article (for example to a web site) without written permission from the original author. Failure to do so is a violation of copyright laws.
3) You may link to this article from another website, but ONLY if it is not wrapped in a frame.
4) You will abide by any additional copyright restrictions which the author may have placed in the article or article's description. |
|
Report Bad Submission |
|
|
Your Vote! |
See Voting Log |
|
Other User Comments |
5/27/2003 6:22:51 AM:Elfar Alfreğsson why should you change the version
number?
|
5/27/2003 6:25:44 AM:Elfar Alfreğsson I mean the Product version number.
|
5/27/2003 6:26:30 AM:Elfar Alfreğsson bleh pushed enter to quickly again.
is
that the version number of the studio
or the one of the solution?
|
5/27/2003 8:26:28 AM:Unruled Boy the one of Visual Studio .net
|
5/28/2003 12:07:22 AM:Thushan Fernando you shouldnt do this unless your sure
your not using any .NET v1.1 code,
thats the reason why they did
this.
BE CAREFUL!
|
5/28/2003 12:33:54 PM:Unruled Boy to:Thushan Fernando
right, VS.NET
1.1 has some new functions that cannot
be compiled in VS.NET 1.0, but this
article simply show people how to
convert 1.1 solutions back to 1.0
solutions which are created by 1.0 but
modified by 1.1 or created by 1.1 yet
they do not uses 1.1 function.
|
5/29/2003 1:46:12 PM:Carl Mercier This works like a charm! Thanks!
|
5/29/2003 9:56:25 PM:Unruled Boy i am now developing an application to
auto convert between vs.net 2003 and
vs.net 2002. hope that it will be
finished in few days.
|
6/15/2003 7:00:58 PM: This article oversimplifies it. What
about the references? You cannot
compile 1.1 code with Visual Studio
2002. It's fine if you have no code.
|
9/23/2003 3:35:54 AM:Dean Kruger Thanks!
|
|
Add Your Feedback! |
Note:Not only will your feedback be posted, but an email will be sent to the code's author in your name.
NOTICE: The author of this article has been kind enough to share it with you. If you have a criticism, please state it politely or it will be deleted.
For feedback not related to this particular article, please click here. |
|