Bryant Likes

Wow, thats quite a big amount of overhead.
<br>
<br>I'm suprised, and yes, a good reason to have a std C# class along side your project to handle expressions too complex

Bryant,

According to your explaination the lines of code executed between the two lines is 20 and the reason which you gave is the saving of states. BizTalk Orchestration has persistent points which are used to save the state of an orchestration to the SQL Server database and it can rehydrate (get active) and start running from its last persisted state.

However the lines of codes you have mentioned is not true for the expression shapes. You cannot tell the exact amount of code or process that executed between the shapes. If you compile your orchestration you can get the C# version of the orchestration and you can see the code generated from the orchestration.

Regarding the persistent points there are some shapes at which persistent points are created like Send/Receive and atomic scopes. Not on every expression shapes are persistent points created.

The solution which you gave explains that if you use an external C# assembly and call it in the expression shape you can save the 20 lines of codes which is not true. BizTalk will still create persistent points and usually there is an extra overhead in calling the external procedures from assembly as the assembly is loaded cached and executed.