http://blogs.msdn.com/b/dsvc/archive/2010/06/15/vs2010-unable-to-hit-breakpoints-in-managed-code.aspxIn Visual Studio 2010, if you are debugging a native executable which in turn loads a managed DLL built against a version of the framework previous to version 4, you may find that breakpoints which are set in the managed code are not hit. The breakpointsen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/dsvc/archive/2010/06/15/vs2010-unable-to-hit-breakpoints-in-managed-code.aspx#10399482Tue, 05 Mar 2013 12:44:23 GMT91d46819-8472-40ad-a661-2c78acb4018c:10399482Umesh Marathe<p>I can&#39;t see any code type to debug in select dialog box while try to debug the managed code..</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10399482" width="1" height="1">http://blogs.msdn.com/b/dsvc/archive/2010/06/15/vs2010-unable-to-hit-breakpoints-in-managed-code.aspx#10307899Mon, 21 May 2012 04:22:53 GMT91d46819-8472-40ad-a661-2c78acb4018c:10307899beilon<p>I have a C++ application which references a C# COM object dll. Both are targeted to .Net 4.0 but still the C# breakpoints are not hit with the error above. Note that this happens when running the Debug configuration and not when running the Release configuration. Using the suggestion above did not resolve the issue. Any tip for this situation?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10307899" width="1" height="1">http://blogs.msdn.com/b/dsvc/archive/2010/06/15/vs2010-unable-to-hit-breakpoints-in-managed-code.aspx#10148737Fri, 01 Apr 2011 13:05:22 GMT91d46819-8472-40ad-a661-2c78acb4018c:10148737Got hit by this..<p>work around works tho!</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10148737" width="1" height="1">http://blogs.msdn.com/b/dsvc/archive/2010/06/15/vs2010-unable-to-hit-breakpoints-in-managed-code.aspx#10100694Mon, 06 Dec 2010 09:39:45 GMT91d46819-8472-40ad-a661-2c78acb4018c:10100694beornC<p>Also, the &quot;app.config&quot; file needs to be named after the file you specify in the &quot;start external program&quot; textbox.</p> <p>So if I&#39;m using Notepad and want to debug it the app.config should be named &quot;notepad.exe.config&quot;!!</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10100694" width="1" height="1">http://blogs.msdn.com/b/dsvc/archive/2010/06/15/vs2010-unable-to-hit-breakpoints-in-managed-code.aspx#10037754Tue, 13 Jul 2010 20:12:07 GMT91d46819-8472-40ad-a661-2c78acb4018c:10037754Riddell<p>This bug just bit me today. I&#39;m trying your suggested fix right now. Is there anywhere that I can monitor the status of this bug?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10037754" width="1" height="1">