I'm using SMC v4.0.2, C#, and the .NET Compact Framework and when I push to a new state I catch a MissingMethodException for System.Diagnostics.Trace.WriteLine(). (This doesn't happen with a simple transition.) I'm compiling without the -g option and I can see that FSMContext.Debug is false.
I've looked at your source code for FSMContext.cs and I see that each call to Trace.WriteLine is wrapped in a test of Debug==true so I don't understand why the exception is being thrown?
Do you call Trace.WriteLine elsewhere without testing the Debug property?
Could you use Reflection to call WriteLine and silently catch the MissingMethodException (do nothing with the exception but let the program continue)?
Do you have any other ideas?
Thanks,
Bill
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using SMC v4.0.2, C#, and the .NET Compact Framework and when I push to a new state I catch a MissingMethodException for System.Diagnostics.Trace.WriteLine(). (This doesn't happen with a simple transition.) I'm compiling without the -g option and I can see that FSMContext.Debug is false.
I've looked at your source code for FSMContext.cs and I see that each call to Trace.WriteLine is wrapped in a test of Debug==true so I don't understand why the exception is being thrown?
Do you call Trace.WriteLine elsewhere without testing the Debug property?
Could you use Reflection to call WriteLine and silently catch the MissingMethodException (do nothing with the exception but let the program continue)?
Do you have any other ideas?
Thanks,
Bill