- This topic has 7 replies, 1 voice, and was last updated 7 years, 3 months ago by
.
-
Posts
-
-
I’m trying to debug a custom component and step through the code by attaching to BTSNTSvc.exe. I can duplicate this behavior with my component and even with the FixMsg Pipeline component included with the Biztalk 2004 Samples.
When I attach to BTSNTSvc.exe and set a breakpoint, a question mark appears in the break point and the message, “…breakpoint will not currently be hit. No symbols have been loaded…”
The strange thing is, if I attach to another instance of Visual Studio that is using a pipeline utilizing my component, the breakpoints work fines (putting breakpoints in the IBaseComponent properties).
I’ve deployed the component to the GAC and verified that I am using Debug when compiling. I’m stumped.
-
-
Are you sure you’re attaching to the right host intance? If you have multipe host instances, you will have multiple instances of BTSNTSVC. If you are already on the right host, have you tried rebuilding, redeploying, restarting Studio, and restarting the host instance?
-
-
Although I had the custom component set to build using Debug, the receive pipeline it was beign utilized in was set to build under Deployment. Once I changed it to Development an did a rebuild, the breakpoint was hit. Thanks for the help.
-
when i am attaching process BTSntsvc.exe in visual studio 2008. i am doing following thing before it.
a) Building teh component in debug mode. b)pipeline in debug mode. C) building the solution…keeping output path as C:/programfiles/microsoftbiztalk server 2009/pipelinecomponents/ d) placing the dll in gacutil. e) deploying the solution.. I have given break point in pipeline component. but its not stooping, when i am placing xml file to receive location…..I tried every possibility which i got from forum but still its not woking. Could any one sujjest me any solution…
Thanks in advance.
Ashwani Kumar
-
You can get your PDB file in the Bin/Debug folder of your application manually copying it to GAC too, the default path looks some thing like C:\Windows\Microsoft.NET\assembly\GAC_MSIL\%componentNmae%\%Version%\, it this desen't work , try also copying this PDB file inti pipeline component folder
-
It is not necessary to GAC Pipeline Components; BizTalk will look in the Pipeline Components folder here — C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\Pipeline Components. However, if you do inadvertently GAC your Pipeline Component, i.e. if you import an MSI containing the component (and you have 'GAC on Import' or one of the other GAC-ing options selected) you will run into this problem. The best thing to do is search the GAC here: C:\Windows\Microsoft.NET\assembly\GAC_MSIL and if you have a folder in this folder named after your Pipeline Component, then delete that folder. BizTalk will then return to looking for your pipeline component in the C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\Pipeline Components folder (after failing to find it in the GAC). You *should* need to stop the BizTalk Host Instance (that's running the Send Port or Receive Location containing a Pipeline that's using your Pipeline Component) in order to copy a new version of the DLL into the C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\Pipeline Components folder. Windows *should* tell you that the file (DLL) is in use and cannot be overwritten. So if you can copy a new version of the DLL into the C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\Pipeline Components folder then that's a sure sign that your Pipeline Component is GAC-ed and that's why Visual Studio is unable to go into Breakpoint on the updated code.
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.