Readme Specifies Non-Optimal CsProj property for Dynamic Loading

[Sewer56]

In short:

In the usage section of your library, you specify the usage of the GenerateRuntimeConfigurationFiles to ensure that loadable assemblies are created. While this works, the advised property to set for end users is instead EnableDynamicLoading property.

Or to quote Mr Vitek Karas, one of the .NET Runtime developers.

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.

(original text)

A few years ago I made the same mistake too, albeit all of the new properties weren't yet fully documented then.

[chyyran]

Thanks for pointing this out. Fixed in 0a6bf78