MIPPlugin path to Express 2017 R3 Management Client?

My plugin, made for Smart Client, Event Server and Management Client, works fine in Express+. When installed on a Express R3, it only works in Smart Client and the Event Server. I’ve tried the following:

[C:\Program](file:C:/Program) Files (x86)\Milestone\Milestone Surveillance\MIPPlugins\*myplugin*

[C:\Program](file:C:/Program) Files (x86)\Milestone\MIPPlugins\*myplugin*

and of course:

[C:\Program](file:C:/Program) Files\Milestone\MIPPlugins\*myplugin*

Where’s it supposed to be installed? Any way to debug this?

To have the plugin load in the 32 bit Management Application use either

[C:\Program](file:C:/Program) Files (x86)\Milestone\Milestone Surveillance\MIPPlugins\*myplugin*

or

[C:\Program](file:C:/Program) Files (x86)\Milestone\MIPPlugins\*myplugin* (recommended)

both should work.

If the plugin loads you can see it in the Help -About dialog.

Start Debugging from Visual Studio This Way:

-Place the compiled DLLs in the folder that is loaded by the application. You may want to make a copy statement in the post-build event command line on the Build-Events tab within Visual Studio.

-Create a plugin.def file and place it in the same folder.

-Change Visual Studio project properties for Debug

--Change the Start external program so that it matches the application that should start (for the XProtect Smart Client it would be Client.exe in the XProtect Smart Client install folder) (for the Management Application it would be “[C:\Program](file:C:/Program) Files (x86)\Milestone\Milestone Surveillance\ManagementApplication.exe”).

I did not realize the Management Application on the older Express version was running 32 bit. I changed the platform target on my DLL’s and swapped the references to their 32bit counterparts. Works now!