I figured it out. I had to wrap the entire scope which contained shapes there were utilizing my helper libraries in another scope as well. It appears that the .dlls (for the helper class library) must have been getting loaded and evaluated as soon as the scope is reached.
If you look at the attached image, my helper libraries are used in the "ValidateWrapper" expression shape, but the orchestration wasn't even making it there before a MissingMethodException
was being called (due to a missing method in the helper class library), the "GeneralScope" shape was not able to catch the MissingMethodException
but as soon as I wrapped the GeneralScope in another scope, the MissingMethodException
was caught by that and could be handled.
This all happened because I updated the helper class resource through BizTalk admin console so the compiler wasn't able to warn of the missing method...but at least now I know I can catch the exception should it happen again.