Dr. Damir Dobric
Dr. Damir Dobric
@michaelgsharp, once I have a simplified application with this issue, I will come back to this. The current application is just too complex and it would take me a long...
Just as additional info. It might be helpful to fix the issue. Following code blocks inside *Dispose*. ` CancellationTokenSource tSrc = new CancellationTokenSource(); Console.CancelKeyPress += (obj, arg) => { Console.WriteLine("Cancel...
Why should that not be supported? It is a must-feature.
This is the version of the fluent API that I use: ``
Anything new? I would recommend providing in the API a generic approach to all other properties that might be used in the future. With this developers can use them even...
Any comments on this?
I'm not sure about OnFunctionResult. I'm invoking the function on the input event.  Hope this helps.
Whatever the right event might be, the framework MUST NOT THROW in this case. The argument functionName specifies the function which should be invoked. @feiyun0112 I'm not looking for a...
Hi Sergey, thanks for your response. Honestly, I have also never seen this behaviour before. But I also never used so many arguments. Step by step, we are trying to...
I have figured out the following, which seems to be a bug: All value-type arguments that are marked as nullable (int?, SomeEnum?, DateTime?... ) are correctly passed to the model...