Ralf

Currently this optimization is only supported for closed types. For open types (generics) we can not fetch the method information on compile time because the generics are compiled during runtime....

Support for open generics was implemented in [v2.0.144](https://www.nuget.org/packages/MethodBoundaryAspect.Fody/2.0.144) Overhead for open generic methods is bigger because they can not efficently cached at compile time like closed generic or non-generic methods....

> > > Looks great, thank you, I'll give it a try! Anyway, I still think that for special cases (eg. generics now) it would be fine if calling GetCurrentMethod...

this has to be configurable at the aspect level. If I have time i will investigate this

@mjvh80 so the solution would be to identify the compiler generated state machine class and skip weaving anything in it?

To run the sample the following package references are required: ``` ```

I dont understand what information you need from me. Can you rephrase your question? The only workaround I found was to split the workflow creation into multiple methods so each...

Thx for the tip! I was successful using an own implementation of the IWorkflowExecutor. Now the workflow can be run stepwise... perfect for unittesting when setting mocks and verifications per...

For reference: I created a base class for my unittests in case someone else needs something similar: ``` using Microsoft.Extensions.DependencyInjection; using Microsoft.Extensions.Logging; using Moq; using WorkflowCore.Interface; using WorkflowCore.Models; using WorkflowCore.Testing;...

Yes, starting the APK before "Connecting to ACE server" works!