Plugins in Modlr
m ((username removed) (log details removed): Moving to Documentation namespace) |
(Automatically adding template at the end of the page.) |
||
| Line 21: | Line 21: | ||
[[File:2018-01-08 10h57 06.png|none|thumb|343x343px]] | [[File:2018-01-08 10h57 06.png|none|thumb|343x343px]] | ||
[[Category:MDriven Designer]] | [[Category:MDriven Designer]] | ||
{{Edited|July|12|2024}} | |||
Revision as of 15:45, 10 February 2024
This page was created by Hans.karlsen on 2018-01-08. Last edited by Stephanie on 2025-02-03.
The Modelling logic central to MDrivenDesigner and MDriven for VisualStudio has a Plugin infrastructure.
The infrastructure is described in further detail here: Modlr plugin
It loads plugins located in the path, decided by this code: (Strikeout is replaced with the new value 20230125 due to OneDrive sync issues.)
private const string RegKeyName = @"Software\CapableObjects\Modlr";
public static void LoadPlugIns()
{
string path = Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData.LocalApplicationData);
path += @"\CapableObjects\MDriven\Plugins";
Microsoft.Win32.RegistryKey key = Microsoft.Win32.Registry.CurrentUser.OpenSubKey(RegKeyName);
if (key != null)
{
path = key.GetValue("PluginPath",path) as string;
}
System.IO.Directory.CreateDirectory(path);
LoadPlugInAssemblies(path);
}
As the code shows, you can override that path by creating a registry value:
