IFEO and Managed-debugginghttp://blogs.msdn.com/b/jmstall/archive/2006/02/16/ifeo-managed-debugging.aspxBe careful of Image File Execution Options (IFEO) with managed debugging - it won't work like you expect.
IFEO lets you set some registry goo such that when you launch a target app (specified by a registry key name), a debugger (specified by a stringen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)Image File Execution Options or how to start the debugger automaticallyhttp://blogs.msdn.com/b/jmstall/archive/2006/02/16/ifeo-managed-debugging.aspx#747576Sat, 09 Sep 2006 10:39:36 GMT91d46819-8472-40ad-a661-2c78acb4018c:747576Tiho's blogI'm putting this here so that I don't forget where to look for it later when I need it&amp;amp;nbsp;as it has...<img src="http://blogs.msdn.com/aggbug.aspx?PostID=747576" width="1" height="1">re: IFEO and Managed-debugginghttp://blogs.msdn.com/b/jmstall/archive/2006/02/16/ifeo-managed-debugging.aspx#534304Fri, 17 Feb 2006 22:35:22 GMT91d46819-8472-40ad-a661-2c78acb4018c:534304Mike Stall - MSFTAdrian -
<br>1. IFEO works great for native + interop-debugging; this is just an issue for managed-only debugging.
<br>2. This has nothign to do with VS. Any other managed debugger (eg, MDbg) would have the same problem.
<br><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=534304" width="1" height="1">re: IFEO and Managed-debugginghttp://blogs.msdn.com/b/jmstall/archive/2006/02/16/ifeo-managed-debugging.aspx#534239Fri, 17 Feb 2006 21:16:08 GMT91d46819-8472-40ad-a661-2c78acb4018c:534239Adrian EidelmanSo isn&#180;t it possible to launch an exe file and debug it with Visual Studio debugger from the beginning as you can do with others debuggers ?<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=534239" width="1" height="1">Interesting Findshttp://blogs.msdn.com/b/jmstall/archive/2006/02/16/ifeo-managed-debugging.aspx#534069Fri, 17 Feb 2006 16:45:25 GMT91d46819-8472-40ad-a661-2c78acb4018c:534069Jason Haley<img src="http://blogs.msdn.com/aggbug.aspx?PostID=534069" width="1" height="1">Interesting Findshttp://blogs.msdn.com/b/jmstall/archive/2006/02/16/ifeo-managed-debugging.aspx#534064Fri, 17 Feb 2006 16:41:37 GMT91d46819-8472-40ad-a661-2c78acb4018c:534064Jason Haley<img src="http://blogs.msdn.com/aggbug.aspx?PostID=534064" width="1" height="1">re: IFEO and Managed-debugginghttp://blogs.msdn.com/b/jmstall/archive/2006/02/16/ifeo-managed-debugging.aspx#533715Fri, 17 Feb 2006 02:30:56 GMT91d46819-8472-40ad-a661-2c78acb4018c:533715Mike Stall - MSFTYes, windbg/sos is native-debugging and so everything should work as intended.
<br>I was focusing more on Visual Studio and ICorDebug-based debugging.<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=533715" width="1" height="1">re: IFEO and Managed-debugginghttp://blogs.msdn.com/b/jmstall/archive/2006/02/16/ifeo-managed-debugging.aspx#533698Fri, 17 Feb 2006 02:10:55 GMT91d46819-8472-40ad-a661-2c78acb4018c:533698David DouglassYou say to be careful with &quot;managed debugging&quot;. &nbsp;So, if I want to debug managed code using WinDbg/SOS, will it work as expected?<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=533698" width="1" height="1">