C# script output path dependent on when scripting DLL gets loaded about omodframework HOT 4 CLOSED

Update: Apparently they made .NET lazier than I thought and the static fields of DotNetScriptHandler get initialised the first time a DotNetScriptHandler is built or something tries to access them, so there's very little I can do as a user of this library.

from omodframework.

There's a similar issue with the DLL path, actually. If that setting gets changed too late, then the script handler will have been statically initialised with the default value, which as per #24, isn't a suitable value.

It's probably safer just to construct a new CompilerParameters object each time, or at least update the fields which are based on settings. That way, you're not at the mercy of Microsoft deciding that changing static initialisation order is a good idea again, and also can support the weird things I've decided to do.

from omodframework.

I'll make up a PR in a bit.

from omodframework.

AnyOldName3/modorganizer-installer_omod@add15c1 is a viable workaround on MO2's side, but unlike #32, is liable to break if the .NET runtime decides to change static initialisation order again.

from omodframework.