Visual Studio 2012 cannot debug a native EXE or DLL created with Visual C++ 6 - by PaoloPablito

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 772222 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 11/26/2012 5:59:46 AM
Access Restriction Public


Visual Studio 2012 cannot debug a native application created with Visual C++ 6.0, while other debuggers can.
The problem occurs with live debugging, post-mortem debugging and minidump analysis.
The problem applies to both EXE and DLL binaries (if you have an EXE built with VS 2012 that uses a DLL built with VS 6, you may have problems e.g. with crashes).
Sign in to post a comment.
Posted by Microsoft on 1/15/2013 at 3:56 PM

We had another round of investigation regarding the reporting of similar/related issues and that scenario seems a lower priority relative to other customer requests. Unfortunately we have to decline the request at the time being. We will keep you informed if priorities change.

Posted by PaoloPablito on 12/7/2012 at 2:59 AM
p.s. I switched back the status to Active because I'd like Microsoft to think about my reply (December 2nd)
Posted by PaoloPablito on 12/2/2012 at 11:50 PM
Why? Do you think this scenario is uncommon? It's probably more common than you think. You know that there are a LOT of legacy DLLs compiled with VS 6 out there, don't you? At the moment, at our company, there are many VS 2010 projects (some managed, some native) that must still interoperate with third-party libraries that were created with Visual C++ 6. Next year we'll probably migrate our projects to VS 2012, but the external dependencies won't go away like magic. We cannot rebuild third-party components as we of course don't have source code, and we cannot reinvent them from scratch. According to Murphy's Law, bugs and crashes WILL occur. So you are forcing us to develop with VS 2012 but to debug with VS 2010 or older (or with the user-unfriendly WinDbg)
Posted by Microsoft on 11/30/2012 at 3:36 PM

Unfortunately, we currently have no plans to support such debugging scenario.

Ayman Shoukry
Posted by PaoloPablito on 11/28/2012 at 4:26 AM
Update: unfortunately, I reproduced the problem even after installing the Update 1 of Visual Studio 2012.
Posted by Microsoft on 11/26/2012 at 8:57 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 11/26/2012 at 6:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(