RE: Problem debugging External Assembly
- From: Yossi Dahan <yossi.dahanREMOVE@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 14 Sep 2007 04:20:01 -0700
Yes it does, which does mean I'm out of ideas!
I have to admit I have had cases where attaching did not work and I thought
there was no reason for it not to but it pretty much always came done to one
of these..
Just to clarify - what I meant in point a -
with all this hosting and caching bussiness in BizTalk it is quite often
that I think a change I've made to a process is loaded, but in fact BizTalk
is still running an older version of it, so code I though should be called is
not acutally being called.
I gotten into the habit of adding trace lines to my processes so when in
doubt I simply add a trace line indicating the new call/change so when I run
the process I know for sure the latest code is being run.
--
Yossi Dahan
http://www.sabratech.co.uk/blogs/yossidahan
"Mark Perry" wrote:
Thanks for the response..
a) I'm sure that it's actually running in the fact that the code is on my
laptop in front of me, and the class / method is being called by the
Orchestration. Maybe we have different understandings of 'actually running'?
b)Checked this, re-built and redeployed to GAC and restarted host instance
c) I've set Biztalk to run under the domain biztalk account
(domain\biztalkuser). When I attach Visual Studio to a process and enter the
name of the remote server it displays a list of things to attach to; one of
these is BTSNCSvc.exe with the username domain\biztalkuser
So I think (apart from possibly a)) that I've done everything correct.
"Yossi Dahan" wrote:
This can be caused by several things - I would verify that -
a) you're sure the code you're intending to debug is actually running
b) the version of the code you have is the same as the version on the server
c) you are attached to the correct Biztalk host
--
Yossi Dahan
http://www.sabratech.co.uk/blogs/yossidahan
"Mark Perry" wrote:
I have written a .dll to write some stuff to a SQL log table and I'm calling
the methods at numerous points in an Orchestration. I know that something is
wrong with the assembly because the messages that were flowing through the
system before I added it have stopped working.
So I'm trying to debug the assembly remotely. I have run the Debugging
Remote Monitor on the server that I'm developing onto, attached the BTS
service process to the project on my laptop but nothing happens - none of the
break points that I have set are being triggered.
When I set the break points they turn into empty red circles and I get the
message 'The breakpoint will not currently be hit'. Also, when I put a
message into the system I can see visual studio loading 'things' right at the
bottom, but my breakpoints never get hit.
Can anyone suggest what is going wrong? I've been able to debug external
assemblies before but that was when I was running VS on the server that I was
developing on. Now I'm debugging remotely laptop to server it's not working.
- Prev by Date: Re: Timespan(0) in listen shape, what does it mean?
- Next by Date: Re: Problem debugging External Assembly
- Previous by thread: How to: Only authorized Active Directory group could post messages to BizTalk WebService port
- Next by thread: Re: Problem debugging External Assembly
- Index(es):
Relevant Pages
|
