CODEWITHSUNDEEP
c#workflow-foundation-4workflow-foundationworkflow-rehosting
Olaru Mircea
Olaru Mircea

Reputation: 2620

Strange exception catching in workflow foundation

In one of my projects i am adding a reference to another project which contains a rehosted designer for WF4. My scenario is as follows: 1. Load a worklflow from an existing xaml file. 2. Throw an exception in my main application.

At this point, i got a nice message box with title "Workflow Designer" and with the full stack trace of the exception. It's like when loading that workflow into it's designer surface, a mechanism starts somewhere which handles my entire app.

I have to mention that, without loading the workflow from the xaml first, when throwing the exception, my app will crash.

I cannot understand how is that possible, what's the thing in that other project that takes care of my entire application exceptions handling..

enter image description here

As you may see in this pic, the exception is thrown at : AEE.Tools.Unicom.Frames.ByteFrame.Assign method. Indeed i don't have a try catch there and it would be normal for my app to crash.

I have this in my Output: 

 A first chance exception of type 'System.NullReferenceException' occurred in AEE.Tools.UnicomNeEva.dll

 The thread '<No Name>' (0x2c50) has exited with code 0 (0x0).

 Step into: Stepping over non-user code 'MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen'

Does anyone know if i can stop this from interfering ?

Upvotes: 0

Views: 217

Answers (0)

Related Questions