Violated constraint during runtime with pipeline simulation from a plugin step without an instance

[SvenRahnSIT]

I am using FakeXrmEasy v2.8.0.

When registering a plugin step without an instance like

context.RegisterPluginStep<Plugin1>(new PluginStepDefinition()
{
    MessageName = Plugins.Utils.Utils.MessageNames.Update,
    EntityLogicalName = Account.EntityLogicalName,
    Stage = FakeXrmEasy.Abstractions.Plugins.Enums.ProcessingStepStage.Postoperation,
});

and then causing the step to trigger with an update, FakeXrmEasy tries to build the method handle to ExecutePluginWith, which has the type parameter T with a constraint to IPlugin and new(). My plugin doesn't have an empty constructor, it only has the one with both config string parameters. This error is thrown during runtime:

System.ArgumentException: GenericArguments[0], 'Core.Plugins.Account.Plugin1', on 'Microsoft.Xrm.Sdk.IPlugin ExecutePluginWith[T](FakeXrmEasy.Pipeline.Scope.EventPipelineScope)' violates the constraint of type 'T'.

The CRM handles this just fine but FakeXrmEasy doesn't like it.

Please either handle this correctly while constructing the method handle or add a new() constraint on RegisterPluginStep to catch this during compilation.

[jordimontana82]

@SvenRahnSIT sorry for not getting back to you before.

The plugin step definition has a property to pass in Security configurations, did you try that already, and if not, could you try setting them there?

[SvenRahnSIT]

@jordimontana82 The plugin doesn't have any configuration, so none is provided in the step. The plugin doesn't have an empty constructor. The constructor is the one with two parameters:

public class TestPlugin : IPlugin
    {
        public TestPlugin() (string? unsecureConfig, string? secureConfig) {}

        public void Execute(IServiceProvider serviceProvider)
        {
        }
    }

That's how the error happens.

[jordimontana82]

@SvenRahnSIT thanks, according to your plugin example, you should use the plugin step definition that takes the secure and unsecure configs (it's the constructor in your example with the 2 strings), even if they are not used in your plugin. In the platform, a plugin has either an empty constructor or the secure / unsecureConfigs constructor.

If you don't need to use any unsecure or secure configs, maybe an empty constructor might be better choice for your plugin.

Hope this helps!