Sometimes it's not possible to load an assembly with reflection due to limitations and fine print about how .NET loads assemblies dynamically. As a workaround for these limitations, I suggest enabling projects to output their own data model info on startup using Assembly.GetExecutingAssembly as the basis. This requires users to add some special startup code to their application that will output a library's data model as json to the app's bin directory. ModelSync will then be able to load that json and bypass reflection limitations.
adamfoneil
commented
4 years ago
Sometimes it's not possible to load an assembly with reflection due to limitations and fine print about how .NET loads assemblies dynamically. As a workaround for these limitations, I suggest enabling projects to output their own data model info on startup using
Assembly.GetExecutingAssemblyas the basis. This requires users to add some special startup code to their application that will output a library's data model as json to the app's bin directory. ModelSync will then be able to load that json and bypass reflection limitations.