I'm current investigating a way to move from Visual studio 6.0 to the lastest VS 2005. My project comprises with MFC, stl, and thirdparty libraries. When I test converting it to VS 2005 beta 2 the compiler generated 6500+ error.
Is there a better way to do this? Or is there a compiler switch that make the new compiler compatible with VS6.0 compiler?
Hi supra!
type="cite">I'm current investigating a way to move from Visual studio 6.0 to the lastest VS 2005. My project comprises with MFC, stl, and thirdparty libraries. When I test converting it to VS 2005 beta 2 the compiler generated 6500+ error. Is there a better way to do this? Or is there a compiler switch that make the new compiler compatible with VS6.0 compiler? Errors or warnings? Most warnings will disapear if you define thefollowing: _CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T But it is recommended, that you use the more secure versions of the CRT. Greetings Jochen--
My blog about Win32 and .NETMVPUser at 2007-8-21 >
regards,
supra
You will need to go through the errors. This isn't normally just a compiler issue, but is a combination of compiler conformance and library changes. Generally, the 6500 instances will corespond to a fairly small set of distinct issues. We have done a decent number of porting labs with customers and normally successful in working through all the issues on a large code base in the space of a single day.
For the compiler breaking changes of the 2003 and 2005 release see:
http://msdn2.microsoft.com/library/4162y30b(en-us,vs.80).aspx
If you got lots of these warnings from the Secure CRT libraries, then see the following link for a temporary solution:
http://msdn2.microsoft.com/library/8ef0s5kh(en-us,vs.80).aspx
Ronald Laeremans
Visual C++ team
