3.99.1.7

• fix:
  • FINALLY! binding anything from a AssemblyLoadContext Assembly, e.g. ModScript instances,
    to a WPF control seems to result in WPF pinning the Assembly (caches internally ?).
    changed Build tab to bind to list of new entry class instances instead of ModScript instances,
    this seems to allow mod assemblies to finally be released.
• change:
  • remove all use of static's from included scripts i.e. util and mod,
    in an attempt to prevent pinning cmk mod assemblies in memory.
  • Mod<script_name>() renamed to Script<script_name>().
  • PlayAs<script_name>() renamed to Execute<script_name>();
  • Script<> and Execute<> can now be called for any (mod) script.
• add:
  • ModClass class now has virtual void OnDispose() method that should be overridden
    in mod classes to unhook any events they may have hooked. Failing to do this
    may result in hook pinning the mod Assembly and preventing it from being unloaded.
    An example of this is in the cmk/(Configure) script.