0
Hi
I found a tool on the net which converts the versions of .net framework to take care of the compatibility which takes care of versioning the solution, project, resource files etc.
Tellie
0
This is a complete SWAG (Scientific Wild *** Guess)...
In the solution file, there is a line that tells which version of Visual Studio.NET was used, you can change that to the previous version and see what happens. Open up the solution fild (sln) in Notepad, and change the line.
The line looks like this:
Microsoft Visual Studio Solution File, Format Version 8.0
In VS 2002, the like looks like:
Microsoft Visual Studio Solution File, Format Version 7.0
Then in the project file, you have a header at the top for the language:
And then in Visual 2003, the same one looks like:
That's all that seems to be different, but just remember, that this a complete guess.
John...
0
simple answer, run the same version on both machines. This has been a problem as long as Office has been around. They add lots of new features, and even rewrite a lot of ot, which hurts backwords compatibility