Someone is asking, whether BizTalk develops whether someone in Rad is answering, if you can debug orchestration on the development environment, BizTalk even
Indeed, even if the skilled method I will introduce, I will later re-reile the F11 when I develop .NET, and I can't help but shook my head against BizTalk.
(1) The first point may not be debug orchestration, but it is a relatively easy problem, and can be tested at the time of development, and it is not necessary to wait until Deploy will. I mean mapping, mapping is a more operation in Orchestration. Is there a format XML to be successfully converted into an XML instance of another format, not necessarily, after deploy, in the development environment, in mapping File Property Page Specifies an XML Source file via TestMap Input Instance, then select Test Map to test mapping, which outputs Target XML or Error Report.
(2) If any Orchestration is executed, if there is a problem, it is possible that there will be some error prompts in Application Event View; if you are not detailed, you can find the circulation of the message in the HAT, which step has been judged.
(3) There is Orchestration Debugger in HAT, and the breakpoint can be set in Orchestration and the value of the variable and the export message is checked. The specific operation is as follows: To debug OrcheStraction, the Orchestration requires at least once, so that it can be found in HAT. In Hat -> Report -> Find Message, find the message contained in the Orchestration, right-click the message with the "Orchestration Debugger" option in the pop-up menu, the Debugger interface, you can set the endpoint for each Shape (Shape in Scope can't Set alone). When the next test, the process will execute to stop at the breakpoint, in Hat -> Operation -> Service Instance, you can find the hang of OrcheStance instance via "Runquery", right-click on the "Orchestration Debugger" option, in Debugger Select Debug -> ATTCH, you can check the variables and export messages.
(4) Use Systeminternal's tools DBGView.exe, you can check any of the debug information under the Windows platform, which, written in orchestration's Expression Shape, IStem.Diagnostics.debug.Write ("Hello World"); will be displayed directly DBGVIEW.EXE's window. After DBGVIEW.EXE is downloaded, you can use it directly to open it, you can use it.
To Be Continue ...
