In the SDK\Orchestrations\MethodCall we find an expression shape that contai
ns the following statement:

System.Diagnostics.Debug.WriteLine(iResult);

My question is where does the debug go?  How do I find and read what got wri
tten.

Thanks,
Neal Walters
http://Biztalk-Training.com

[ Post a follow-up to this message ]

Hello Neal,
[vbcol=seagreen]
>In the SDK\Orchestrations\MethodCall we find an expression shape that conta
ins 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.[/
vbcol]

This statement writes a debug output to the "output" window of a debugger, i
f available.
If no debugger is avaialble at the time the statement is executed, the strin
g 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 sen
ding a message)
and in Visual Studio, switch to the output debug window. You will see the st
rings.

Note that this is not specific to an orchestration. If you write a simple "H
ello World" .NET
application with this statement, you will see the asme behavior.

Thanks.
-Gilles.

[ Post a follow-up to this message ]

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.
>

[ Post a follow-up to this message ]