eladho
asked on
Convert a VC++ .NET project to a VC++ 6.0 project
Hi,
I'm using the Visual C++ .NET and wish to convert my project to the previous version 6.0 so as to use another application later on (that must have the previous version).
Is it possible to convert from .NET to 6.0?
Is there any backward compatabilty?
Is there a built-in feature? if not- is there some external application to do that?
Will there be any loss of data? (such that resides on the workspace?)
Thanx,
Elad.
I'm using the Visual C++ .NET and wish to convert my project to the previous version 6.0 so as to use another application later on (that must have the previous version).
Is it possible to convert from .NET to 6.0?
Is there any backward compatabilty?
Is there a built-in feature? if not- is there some external application to do that?
Will there be any loss of data? (such that resides on the workspace?)
Thanx,
Elad.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No, there is no tool to do it...
The way to accomplish what you are trying to do will be create a prject in VC6 and bring it in VS.Net. Good thing is that when VC6 projects are upgraded to S.Net, the orginal V6 project file is not modified. Instead anew file get created. So all your DSW/DSP files stay intact. This makes it very easy to switch between VC6 and VC7. If you add more files to VC7 project, then open the VC6 DSP file and add the same files to it.
The way to accomplish what you are trying to do will be create a prject in VC6 and bring it in VS.Net. Good thing is that when VC6 projects are upgraded to S.Net, the orginal V6 project file is not modified. Instead anew file get created. So all your DSW/DSP files stay intact. This makes it very easy to switch between VC6 and VC7. If you add more files to VC7 project, then open the VC6 DSP file and add the same files to it.
ASKER
I figured that's the case.
I already use the "manual update " mode- updating the .dsw with any change to the .sln .
Well, that's Microsoft... always pushing you... forward ?! :-)
I already use the "manual update " mode- updating the .dsw with any change to the .sln .
Well, that's Microsoft... always pushing you... forward ?! :-)
ASKER
I knew that, but still sometimes things need to be heard a few times before we can really accept them as is... :-)
ASKER
See, I'm trying to compile the same sources on Windoes and Linux. I have to automatically create the .dsp and .dsw files as these are the ones I later use to create "makefiles".
I cannot use V6.0 from the beginning as its compiler is not good enough for me.
What I might try to do, if all else fails, is to use the .NET compiler over V6.0, ignoring whatever other good things the .NET has to offer, and focusing on the critical reason that made me switch to .NET from the beginning.