Jarrod,
We already did this.
To be more precise, what we want to do is to install our dll maybe like a driver before deploying a Veristand project.
This dll should be used by many custom devices.
For the moment, the dll is in every Custom devices. We don't know which one is loaded when the project is deployed.
What we saw is when the are two different versions of the dll because of a human error, the latest one is not loaded.
To avoid such problems, we would like to have only one release of the dll.
All the custom devices, we created, are not necessarily started together that's why it should be deployed before the custom devices.
What we imagine is that a custom device called core (for example) should be created with the dll. The custom device should be always deployed in order to let the other custom devices access to the dll.
It could be done but it's not really smart.
If there is no other possibility, we will do this.
We explore an other way that is to create for example a driver that could be installed using MAX.
It could be a pre requisite before using Veristand with our custom devices.
We don't know if it's possible to create custom driver for MAX, that's why we ask it here.
Is there a way to deploy a dll (using MAX for example and to do it automatically) and what is the best folder to store such files.
Thanks !
Best Regards
CFOE
