Attaching debugger in a macro

[Chris Dunaway]

I am using the following code in a macro to attach to a process:

Dim sFilename As String = "progname.e xe"
Dim proc As EnvDTE.Process
For Each proc In DTE.Debugger.Lo calProcesses
If (Right(proc.Nam e, sFilename.Lengt h) = sFilename) Then
proc.Attach()
attached = True
Exit For
End If
Next

Progname.exe is a VB.Net program compiled in Debug mode.

When it runs, I get an error message that says: "Unmanaged Debugging Not
Available"

How do I attach to a managed program using a macro?
--
Chris

To send me an E-mail, remove the underscores and lunchmeat from my E-Mail
address.

[Visual C# Team]

Unfortunitely, you can't. The automation support for attach in VS.NET 2002
and 2003 was very limited. It didn't let you specify what kind of code that
you want to debug. Instead, it required debugging all the code in the
process. However, it sounds like you have VB.NET, which doesn't support
debugging unmanaged code. You need to either use full VS, or you need to
attach via the processes dialog.

Sorry,

--
Gregg

This posting is provided "AS IS", with no warranties, and confers no rights.
"Chris Dunaway" <dunawayc@_lunc hmeat_sbcglobal .net> wrote in message
news:vm******** *************** *******@40tude. net...

I am using the following code in a macro to attach to a process:

Dim sFilename As String = "progname.e xe"
Dim proc As EnvDTE.Process
For Each proc In DTE.Debugger.Lo calProcesses
If (Right(proc.Nam e, sFilename.Lengt h) = sFilename) Then
proc.Attach()
attached = True
Exit For
End If
Next

Progname.exe is a VB.Net program compiled in Debug mode.

When it runs, I get an error message that says: "Unmanaged Debugging Not
Available"

How do I attach to a managed program using a macro?
--
Chris

To send me an E-mail, remove the underscores and lunchmeat from my E-Mail
address.

[Habib Heydarian [MSFT]]

What version of Visual Studio are you using? It sounds like you're using a
version that doesn't have the native debugging engine. In Visual Studio
2002/2003, the Process.Attach( ) call will attach with the "Native" debug
engine if there's only native code running. If there's managed code, it will
attach in interop mode.

HabibH.

"Chris Dunaway" <dunawayc@_lunc hmeat_sbcglobal .net> wrote in message
news:vm******** *************** *******@40tude. net...

I am using the following code in a macro to attach to a process:

Dim sFilename As String = "progname.e xe"
Dim proc As EnvDTE.Process
For Each proc In DTE.Debugger.Lo calProcesses
If (Right(proc.Nam e, sFilename.Lengt h) = sFilename) Then
proc.Attach()
attached = True
Exit For
End If
Next

Progname.exe is a VB.Net program compiled in Debug mode.

When it runs, I get an error message that says: "Unmanaged Debugging Not
Available"

How do I attach to a managed program using a macro?
--
Chris

To send me an E-mail, remove the underscores and lunchmeat from my E-Mail
address.