BizTalk Server General - How to debug a C# object in ORchestration Debugger

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > July 2005 > How to debug a C# object in ORchestration Debugger





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 How to debug a C# object in ORchestration Debugger
lokesh

2005-07-14, 5:51 pm

Hi
I was wondering is there anyway we can debug the C# object being utilised in
an orchestration through the orchestration debugger.
Jon Flanders[MVP]

2005-07-14, 5:51 pm

Not through the orchestration debugger - but you can through the VS.NET
debugger (or any .NET debugger for that matter).

With VS.NET you
1) Debug menu - then Processes - find the BTSNTSVC.exe process and select
"Attach"
2) Choose to debug the Common Language Runtime
3) Close the attach dialog
4) Set a breakpoint in your code
5) send a message

if step #4 shows a red dot with a question mark - this means that VS.NET
cannot load your symbols because the build in the gac doesn't match the
build that vs.net knows about. The best way I've found to deal with this
is to copy the assembly's pdb file right into the gac folder (this must be
done on the command line)

--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/

"lokesh" <lokesh@discussions.microsoft.com> wrote in message
news:9E23F27E-2964-4AED-95F0-5F2B42B09B79@microsoft.com...
> Hi
> I was wondering is there anyway we can debug the C# object being utilised
> in
> an orchestration through the orchestration debugger.



lokesh

2005-07-15, 5:55 pm

Hi Jon

Thank you for the message. How can i add a pdb file to gac. Itried doing it
through gacutil it didn;t allow me any suggestions

"Jon Flanders[MVP]" wrote:

> Not through the orchestration debugger - but you can through the VS.NET
> debugger (or any .NET debugger for that matter).
>
> With VS.NET you
> 1) Debug menu - then Processes - find the BTSNTSVC.exe process and select
> "Attach"
> 2) Choose to debug the Common Language Runtime
> 3) Close the attach dialog
> 4) Set a breakpoint in your code
> 5) send a message
>
> if step #4 shows a red dot with a question mark - this means that VS.NET
> cannot load your symbols because the build in the gac doesn't match the
> build that vs.net knows about. The best way I've found to deal with this
> is to copy the assembly's pdb file right into the gac folder (this must be
> done on the command line)
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "lokesh" <lokesh@discussions.microsoft.com> wrote in message
> news:9E23F27E-2964-4AED-95F0-5F2B42B09B79@microsoft.com...
>
>
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com