Upgrading vc 2003 project to vc 2008
-
I have a medium sized (27 projects) solution which has a mixture of project types, libs (both MC++ and C++), DLL's (both MC++ & C++) and exes all MC++. I am considering upgrading the project to vc 2008 mainly because this is the only project that I look after that needs VC 2003 and would like to use one development environment for everything. (have successfully upgraded all my VC2005 projects to VC2008) During the upgrade I was considering doing a 'proper' upgrade of all the code e.g. changing __gc class to ref class and using gcnew as required. Anyone know of any undocumented issues that might make this upgrade a failure or accelerate hair loss! Robin
-
I have a medium sized (27 projects) solution which has a mixture of project types, libs (both MC++ and C++), DLL's (both MC++ & C++) and exes all MC++. I am considering upgrading the project to vc 2008 mainly because this is the only project that I look after that needs VC 2003 and would like to use one development environment for everything. (have successfully upgraded all my VC2005 projects to VC2008) During the upgrade I was considering doing a 'proper' upgrade of all the code e.g. changing __gc class to ref class and using gcnew as required. Anyone know of any undocumented issues that might make this upgrade a failure or accelerate hair loss! Robin
I personally would take the time to upgrade all the Managed Extensions code to C++/CLI format. The old syntax is still supported (with a compiler option) but the Managed Extensions are deprecated (and not as clean to read/use as the C++/CLI format). Mark
Mark Salsbery Microsoft MVP - Visual C++ :java: