After several Visual Studio patches and a service pack or two, my MFC source code no longer matches my MFC binaries. When I trace into MFC, I either see assembly or old source code.
How do I get my MFC sources to match my binaries again?
+1
A:
Since there are no other answers I'll tell you the obvious (and the most painful) one. Reinstall everything. And if possible install Visual Studio with SP slipstreamed.
Although I don't know what you meant by "old source", I don't think there were any changes to MFC between Visual Studio 2005 and SP1. But I might be mistaking.
Nikola Smiljanić
2009-12-21 21:47:04
+1
A:
I'm not sure why it's not picking it up automatically - when you build a dll, the source location is stamped in the pdb. Anyway, try setting the source file path in Visual Studio to first point to the "updated" MFC source. If that doesn't work, step into the MFC function again (so you get the "incorrect" source), then close out that file, then browse to and open the "correct" source file. See if the debugger jumps to the appropriate location then.
Terry Mahaffey
2009-12-28 05:36:42
The problem is that I don't have the updated MFC source code. Where can I get that? Some VS service pack updated all the binaries on my machine, but never updated the source code. What can (or should) update the MFC source code? It didn't happen on my machine, so I'll do it manually. Any idea where I can download the MFC sources?
criddell
2009-12-30 21:10:07
+1
A:
There are a number of updates from the MS download centre, searching MFC. but the only one mentioning source is the OLEUI2.cpp update to VS.Net 2003. Maybe it hasn't actually been changed but does need recompiling?
Andy Dent
2010-01-20 14:57:39