I am not sure but some tips:
- You can create an instance of devenv.exe programatically using objDTE =
CreateObject("VisualStudio.DTE"). If you find the ProgID of the CLR-Debugger
(if any), you could control it.
- The DTE object has a Debugger property that you could use to attach and
debug a process, just in case you have to use the VS.NET debugger instead of
the CLR-Debugger.

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com
> Hi,
>
[quoted text clipped - 11 lines]
> Regards
> Rainer
Rainer Queck - 06 Jul 2005 11:52 GMT
Hi Carlos,
thanks for answering.
I am not using VS, I am working with SharpDevelop and there I can not find a
objDTE.
Is DTE common to the framework, or is it something exclusive for VS ?
Regards
Rainer
Carlos J. Quintero [.NET MVP] - 06 Jul 2005 13:16 GMT
DTE is provided by VS.NET (EnvDTE.dll assembly) and it can be used to
control the VS.NET IDE and the Macros IDE. However, the CLR Debugger seems
quite similar to those IDEs (Solution Explorer, etc), so it could be that it
exposes a ProgID that you can use (although I haven´t found it).

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com
> Hi Carlos,
>
[quoted text clipped - 5 lines]
> Regards
> Rainer