| Prasad Sripathi Panditharadhya [MSFT] 2004-06-26, 10:53 am |
| The only way of debugging a map, is to do a TestMap and try out various
input instances and observe the output. Sorry, you cannot debug inline
scripts inside the functoid. I would suggest testing your Inline scripts in
a standalone C# project and then copy paste the code into the functoid once
it is working as expected.
But if you are calling an external .NET assembly from the scripter
functoid, then debugging is possible. You need to open two instances of
Visual Studio. In one instance of VS, open your .NET assembly project and
put break points in the code. In the other VS, open the BizTalk project and
the map. Now from the first instance of VS, debug process and attach it to
second instance of VS. Do a TestMap in the second instance of VS, and you
should be able to hit the break points in your C# project if all goes well
(make sure version info on your .NET assembly is always fixed as in
[assembly: AssemblyVersion("1.0.1.1")]).
If you have lot of code in your inline scripts, then it is probably a good
idea to consolidate the code in an external assembly and call it from your
map, instead of burying the code in your map. You can test/debug the code
much easier outside the mapper.
Thanks....
--------------------[vbcol=seagreen]
<RabiaXavor@discussions.microsoft.com>[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA
03.phx.gbl[vbcol=seagreen]
they are mapped to from the source to the destination schema. THE values
are used in the inline scripts.[vbcol=seagreen]
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
|