Tiny Visual C++ library/example that allows you to inject CoreCLR (the .NET Core Runtime) into the current unmanaged process and execute a .NET library.
In the readme for this project there's a section about troubleshooting - specifically the case of a classlib which doesn't have .runtimeconfig.json by default. Starting with recent .NET Core 3.0 previews (8 for sure, probably earlier) the right way to mark a classlib as a component which will be dynamically loaded is to add <EnableDynamicLoading>true</EnableDynamicLoading> to the project.
Under the hood it does currently set the GenerateRuntimeConfigurationFiles but this may change in the future.
I'm having problems translating this into a DLL startup. I've tried expanding out the bootstrap example to use DllMain and running the CLR from within the attach but injection always fails.
I don't suppose you have any guidance you could give?