ComponentNotRegisteredException thrown when using NUnit Console Runner about autofac

[tillig]

Logically speaking, if it's working in one environment and not another, that's not so much an Autofac problem than it is an environmental issue. Especially in the case of assembly loading - you'll notice Autofac itself isn't what loads or locates assemblies, Autofac just uses what you give it.

From the above, my guess is that there's an assembly that's being found in Visual Studio but is not being found during console runs.

Be aware that the change from a .NET desktop framework to .NET core, and a pretty big jump at that, is not always just lift-and-shift. Especially when it comes to assembly loading, remoting, AppDomains, and the like - there are differences in how .NET Core works. There's also sometimes differences in how things are working in Visual Studio vs console, like Visual Studio handling things like assembly shadow copies during testing differently than the console runner.

In fact, in .NET Core you generally shouldn't be using a specific NUnit or XUnit console runner, you should be using dotnet test - which may also explain why things aren't working as expected.

Much as we love to help folks, we do have some pretty limited bandwidth to help troubleshoot stuff that can't be clearly linked to an issue in Autofac. This, unfortunately, doesn't fall in that category. If you are able to work out a minimal reproduction that very clearly shows it's an Autofac problem, we'd love to see that (likely in a new issue that explains the actual Autofac challenge).