You might also find that the ATL is a good alternative for a lot of the code - since it has come on leaps and bounds since those days. It's probably going to take you less time in the end, and it'll probably give you more education as to what the code is trying to do! Create a bunch of new 2005 projects, and reproduce the application for the new MFC, Win32 API and CRT. Whilst it's probably not what your employer\sponsor wants to hear, it sounds to me like they need to authorise a major refactor so you can do a shallow copy of the code. I've had a bit of a look around and couldn't find much either - however to be honest I think you'll have to build a list of changes between each incremental version of MFC and do it that way yourself.įrom what I can see when 4.2 was ubiquitous we were in the Windows 95/98 days - so there are going to be a whole host of security issues with the code, deprecated methods (in the CRT itself), as well as possible issues to do with unicode strings - since win95 didn't support those out of the box as far as a developer was concerned.