It has come to our attention that versions of MDriven Designer and MDriven Framework for VS2022 fail to start for some users.

The reason for this is some unfortunate residue from older installations of MDriven Framework for VS2019/17.

MDriven Framework for VS2019/17 put some assemblies in the GAC (Global assembly cache) - but MDriven Designer och MDriven Framework does not use the GAC. The ambition is to move away from relying on the GAC in the future.

However, if you have installed older versions of MDriven Framework for VS2019/17, you may experience issues such as those described here:

Problem loading plugins. Exception in 'Modlr.Logic.ModlrLogic', and the Model Designer doesn't run.

or

INNER EXCEPTION: Could not load file or assembly 'GenericFindInWindowControl, Version=7.0.0.13804, Culture=neutral, 
PublicKeyToken=46a833be9e90de8c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. 
(Exception from HRESULT: 0x80131040)

at Modlr.Logic.ModlrLogic..cctor()

The type initializer for 'Modlr.Logic.ModlrLogic' threw an exception.

at Modlr.Logic.ModlrLogic.remove_OnFocusInTree(OnFocusInTreeDelegate value)

at Modlr.ModelEditor.ModlrTree..ctor()

at Gaffr.Form1.InitializeComponent()

at Gaffr.Form1..ctor()

How to Fix These Issues

To resolve these issues, install the latest version of MDriven Framework for VS2019/17. This will refresh the GAC with updated assemblies that work with the newer versions of MDriven Designer and MDriven Framework for VS2022.

or

open GAC C:\Windows\Microsoft.NET\assembly\GAC_MSIL\ and delete the folder and its contents:

• GenericFindInWindowControl
• WECPOFLogic
• Eco.* (all folders matching Eco.*)

After one of these actions, MDriven Designer and MDriven Framework for VS2022 will work as expected.