Re: BizTalk R2 WCF-Net.Tcp Adapter Consumption Issues

Try this.  In the BizTalk admin console, stop the orchestration.  Now run your client.  Now run a query for “All service instances” in the group hub page.  You should have a suspended message.  Open up the message to make sure the data was received correctly.  If the data is right, you can right click on the messae and resume in debug mode.  Right click again and open the message in the orchestration debugger.  Now you can add breakpoints, step through, and check the values of variables and messages.  Alternatively, you could just use a Sysem.Diagnostics.Trace.WriteLine() statement to print out the return value.  Then you can view the trace statement in DebugView.