I’m relying on initialization to register various classes in a factory singleton. Looks like this:
static Registration<MySubclass> registration("MySubclassName");
This works in my stand-alone app version, but in the plugin DLL, only a few of the
Registration constructors are run. I suspect lazy init, since the classes registered are referred to elsewhere in the code, so the compiler knows they must be initialized.
This used to work in the plugin as well (in a released version), but I haven’t touched the code in some time, and have recently upgraded to Visual Studio 2017.
I could simply remove the registration stuff since I don’t really need it, but it would be nice to know if there’s a way I can force all statics to be initialized.