Should we distribute VideoOS.Platform.dll?

MIP
, ,
1

I noticed that one of your plugin samples includes the file VideoOS.Platform.dll. Should we be distributing it and placing it in the plugin directory?

MIPS version 2017R3 supposedly has a fix in it that enables some functionality in my plugin (I’m about to test it). But if the customer doesn’t have an upgraded system, they won’t be able to use that feature of my plugin, unless I include it with the plugin.

I saw another post where you referenced a document about all this, but the link was broken.

I also saw where you have different x86 and x64 installers for MIPS, but your minimum OS does not include any 32-bit versions. What’s up with that?

2

VideoOS.Platform.dll should not be distributed for plugins. This file is part of the installed product.

It is compiled for “Any CPU” - so for any hot-fixes you might receive, it works for both 32 and 64 bit applications.

3

I would like to comment on the subject of minimum OS..

The XProtect VMS requirements are today all 64 bit, but when it comes to clients you can use 32 bit. See - https://www.milestonesys.com/support/resources/system-requirements/ - (go far right to see clients.)

You can build 32 bit clients using the MIP SDK , and you can have Smart Client plug-ins on a 32 bit Smart Client.

4

You might find this discussion on another thread highly relevant -

https://developer.milestonesys.com/s/question/0D50O00003T039DSAR/installing-plugins-on-older-smartclients

5

Thank you both