|
Home > Archive > BizTalk Server General > June 2006 > Debugging Biztalk 2006
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 |
Debugging Biztalk 2006
|
|
|
| Does anybody have information/resources on how to debug in BizTalk 2006?
I have problems with my Orchestration. The application runs without errors
but not generate files in the destination folder.
Thanks
-fj
| |
| Mike Watson 2006-06-29, 7:26 am |
| i tent do put debug.write statements into orchestration expression shapes and
then use a tool like debugview from sysinternals. this is by far the easiest
and quickest way to do it... another good thing about this is that if your
orchestration ports do not change then you do not need to redeploy everytime
you put a debug.write statement in.
just add your debug.write statements, re-compile, re-gac the orchestrations
dll's and then reboot the biztalk process. this will pick up the new lines of
code that you have put in the orchestrations...
cheers,
- mike watson
"fj" wrote:
> Does anybody have information/resources on how to debug in BizTalk 2006?
>
> I have problems with my Orchestration. The application runs without errors
> but not generate files in the destination folder.
>
> Thanks
>
> -fj
>
>
>
| |
|
| Thanks, I'll try that.
I noticed that in Biztalk Administration console, you can setup tracking on
the physical ports in 'tracking' tab. But where do you check the tracking
report?
-fj
"Mike Watson" <mike.watson@discussions.microsoft.com> wrote in message
news:09012BDA-F0B1-4864-90D1-8624A8FF4765@microsoft.com...[vbcol=seagreen]
>i tent do put debug.write statements into orchestration expression shapes
>and
> then use a tool like debugview from sysinternals. this is by far the
> easiest
> and quickest way to do it... another good thing about this is that if your
> orchestration ports do not change then you do not need to redeploy
> everytime
> you put a debug.write statement in.
> just add your debug.write statements, re-compile, re-gac the
> orchestrations
> dll's and then reboot the biztalk process. this will pick up the new lines
> of
> code that you have put in the orchestrations...
>
> cheers,
> - mike watson
>
> "fj" wrote:
>
|
|
|
|
|