|
Home > Archive > BizTalk Server Orchestration > June 2004 > System.Diagnostics.Debug.WriteLine(iResult);
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
System.Diagnostics.Debug.WriteLine(iResult);
|
|
| Neal Walters 2004-06-20, 11:09 pm |
| In the SDK\Orchestrations\MethodCall we find an expression shape that contains the following statement:
System.Diagnostics.Debug.WriteLine(iResult);
My question is where does the debug go? How do I find and read what got written.
Thanks,
Neal Walters
http://Biztalk-Training.com
| |
| Gilles [MSFT] 2004-06-20, 11:09 pm |
| Hello Neal,
>In the SDK\Orchestrations\MethodCall we find an expression shape that contains the following statement:
>
>System.Diagnostics.Debug.WriteLine(iResult);
>
>My question is where does the debug go? How do I find and read what got written.
This statement writes a debug output to the "output" window of a debugger, if available.
If no debugger is avaialble at the time the statement is executed, the string is simply ignored.
To see those strings, attach VS.NET 2003 to BTSNTSVC.EXE and choose ".NET".
Do something that triggers the execution of the statement above (perhaps sending a message)
and in Visual Studio, switch to the output debug window. You will see the strings.
Note that this is not specific to an orchestration. If you write a simple "Hello World" .NET
application with this statement, you will see the asme behavior.
Thanks.
-Gilles.
| |
| Scott Colestock 2004-06-20, 11:09 pm |
| You might want to also just use dbgview.exe - see
http://www.sysinternals.com/ntw2k/f...debugview.shtml
This works great with to see this kind of output.
- Scott Colestock
"Gilles [MSFT]" <Gilles@online.microsoft.com> wrote in message
news:ai9c6tvUEHA.2300@cpmsftngxa10.phx.gbl...
> Hello Neal,
>
contains the following statement:[vbcol=seagreen]
written.[vbcol=seagreen]
>
> This statement writes a debug output to the "output" window of a debugger,
if available.
> If no debugger is avaialble at the time the statement is executed, the
string is simply ignored.
>
> To see those strings, attach VS.NET 2003 to BTSNTSVC.EXE and choose
".NET".
> Do something that triggers the execution of the statement above (perhaps
sending a message)
> and in Visual Studio, switch to the output debug window. You will see the
strings.
>
> Note that this is not specific to an orchestration. If you write a simple
"Hello World" .NET
> application with this statement, you will see the asme behavior.
>
> Thanks.
> -Gilles.
>
|
|
|
|
|