My last 4 blog entries have been on the issues I faced when I compiled some
VC 6 code with VC 2005. It's far from comprehensive and probably covers less
than a quarter of the issues you may run into - but you may find something
useful there : http://blog.voidnish.com/

Signature
Regards,
Nish [VC++ MVP]
> Hi, I'm looking at migrating our existing from Visual Studio (6.00) C++
> code to the .NET version of C++ (unmanaged) Can anyone point me towards
[quoted text clipped - 3 lines]
>
> MD
> Hi, I'm looking at migrating our existing from Visual Studio (6.00)
> C++ code to the .NET version of C++ (unmanaged) Can anyone point me
> towards documention or an overview of this ?
Project conversion is done automagically by a wizard. Now, you could run in
some (rare) incompatibilites due to conformance enhancements in Visual 2003.
See http://msdn2.microsoft.com/en-us/library/ms177251(en-US,VS.80).aspx.
The next point is to take advantage of the new compiler capabilities to
write (or refactor) better code ;-)
Arnaud
MVP - VC
Mike Doyle - 04 Oct 2005 20:43 GMT
>> Hi, I'm looking at migrating our existing from Visual Studio (6.00)
>> C++ code to the .NET version of C++ (unmanaged) Can anyone point me
[quoted text clipped - 10 lines]
> Arnaud
> MVP - VC
Thanks guys. Unfortunately, I think the old programmers were firm believers
in using as many "rare incompatibilites" as possible ;-)
Cheers,
MD