14
An: [EMAIL PROTECTED]
Betreff: Re: [DOTNET] Automatically attaching a .NET process to a debugger
This is not quite what I want. Launch() will start a NEW instance of the
debugger. What I want to do is:
1.I start an application in debug mode within the VS.NET IDE (Debug ->
Start)
2.
This is not quite what I want. Launch() will start a NEW instance of the
debugger. What I want to do is:
1.I start an application in debug mode within the VS.NET IDE (Debug ->
Start)
2.This application starts a second process (a console app which acts as
a remote server)
3.I want this
System.Diagnostics.Debugger.Launch()
-Original Message-
From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of
Urs Eichmann
Sent: Monday, May 13, 2002 10:57 AM
To: [EMAIL PROTECTED]
Subject: [DOTNET] Automatically attaching a .NET process to a debugger
Does anyone know if it's p
If the code is written by you then you can always add the following line
System.Diagnostics.Debugger.Launch at any place and that would launch
the debugger.
I don't know whether you could do that if you don't have the source
code.
-Original Message-
From: Urs Eichmann [mailto:[EMAIL PRO
System.Diagnostics.Debugger.Break()
> -Original Message-
> From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of
> Urs Eichmann
> Sent: 13 May 2002 15:57
> To: [EMAIL PROTECTED]
> Subject: [DOTNET] Automatically attaching a .NET process to a debugger
>
>
> Does anyone know if it'
