Skip to main content

.NET Reflection - The invoked member is not supported in a dynamic assembly.

In the bootstrapping logic of my application I was using some reflection to dynamically register dependencies in the IoC container:

When I was using the same code together with the .NET Core Test server the code above didn't work but resulted in the following exception:

Message: System.NotSupportedException : The invoked member is not supported in a dynamic assembly.

Stack Trace: 

    InternalAssemblyBuilder.GetExportedTypes()

    Assembly.get_ExportedTypes()

    <>c.<ScanForModules>b__5_0(Assembly a)

    SelectManySingleSelectorIterator`2.MoveNext()

    List`1.InsertRange(Int32 index, IEnumerable`1 collection)

    FrameworkBuilder.ScanForModules()

    <>c__DisplayClass0_0.<UseSOFACore>b__1(HostBuilderContext ctx, ContainerBuilder builder)

    ConfigureContainerAdapter`1.ConfigureContainer(HostBuilderContext hostContext, Object containerBuilder)

    HostBuilder.CreateServiceProvider()

    HostBuilder.Build()

    WebApplicationFactory`1.CreateHost(IHostBuilder builder)

    WebApplicationFactory`1.EnsureServer()

    WebApplicationFactory`1.CreateDefaultClient(DelegatingHandler[] handlers)

    WebApplicationFactory`1.CreateDefaultClient(Uri baseAddress, DelegatingHandler[] handlers)

    WebApplicationFactory`1.CreateClient(WebApplicationFactoryClientOptions options)

    WebApplicationFactory`1.CreateClient()

    ConversionApiTests.ctor(SelfHostedApi fixture) line 19

This is because an Assembly is generated dynamically during the tests and the "GetExportedTypes()" is not supported on these assemblies. 

To fix the error I updated the code to remove dynamic assemblies from the iteration:

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more