Process X can't tell if Process Y is being managed debugged.http://blogs.msdn.com/b/jmstall/archive/2005/09/20/remote-managed-debugger-attached.aspxFrom the mail bag: Is there a way to determine if a managed debugger is already attached to a given process id? It looks like ICorDebug.CanLaunchOrAttach might be the right API for this (wouldn't it return FALSE if another debugger isen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)Managed vs. Native debugging APIshttp://blogs.msdn.com/b/jmstall/archive/2005/09/20/remote-managed-debugger-attached.aspx#655413Mon, 03 Jul 2006 21:19:37 GMT91d46819-8472-40ad-a661-2c78acb4018c:655413Mike Stall's .NET Debugging BlogFxCop has a great rule (UseManagedEquivalentsOfWin32Api) to tell you about managed APIs that exist instead...<img src="http://blogs.msdn.com/aggbug.aspx?PostID=655413" width="1" height="1">re: Process X can't tell if Process Y is being managed debugged.http://blogs.msdn.com/b/jmstall/archive/2005/09/20/remote-managed-debugger-attached.aspx#472048Wed, 21 Sep 2005 01:50:30 GMT91d46819-8472-40ad-a661-2c78acb4018c:472048Mark PearceThanks for that tip - I've added the un-managed debugger check to the code in my .NET-based &quot;Fighting the Software Pirates&quot; article.<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=472048" width="1" height="1">