# Run Multiple Versions of Custom Modules

**URL:** <https://forum.inductiveautomation.com/t/run-multiple-versions-of-custom-modules/11855>\
**Category:** Module Development\
**Created:** [June 23, 2016, 9:16pm UTC](https://forum.inductiveautomation.com/t/run-multiple-versions-of-custom-modules/11855 "2016-06-23T21:16:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rnovak](https://avatars.discourse-cdn.com/v4/letter/r/e68b1a/32.png) [@rnovak](https://forum.inductiveautomation.com/u/rnovak)\
**Post date:** [June 23, 2016, 9:16pm UTC](https://forum.inductiveautomation.com/t/run-multiple-versions-of-custom-modules/11855/1 "2016-06-23T21:16:14Z")

</div>

Hello,

We’re in the process of developing a custom module and would like to know if it is possible to install multiple versions of the same module on the same gateway and somehow associate each version with a particular Ignition project. The reasoning behind this is that we want to push out a snapshot of our custom module and allow the customers to play with the Ignition application that utilizes it. In the mean time we would like to continue with the development of the module expanding its capabilities. So we’re essentially thinking that we’ll have a customer version of the module and a development version. We were thinking that we would have a separate build for each version and each version would have a uniquely named set of jars for all custom jars. It’s possible that the entry point class for each module would also need a unique name. We would also have two Ignition projects, one for the customer and one for development. The question we have is whether this is possible or not and if so, how can we accomplish it.

Thank you,  
Richard

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 24, 2016, 4:11am UTC](https://forum.inductiveautomation.com/t/run-multiple-versions-of-custom-modules/11855/2 "2016-06-24T04:11:23Z")

</div>

I’m pretty sure you’ll need to use different module id’s to load into one server. Is there any reason you can’t use multiple virtual machines? I run a dozen or so on my laptop for various customers and various testing activities.

---

<div class="post-metadata">

**Author:** ![PRAMANJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pramanj/32/66935_2.png) [@PRAMANJ](https://forum.inductiveautomation.com/u/PRAMANJ)\
**Post date:** [July 22, 2016, 1:54pm UTC](https://forum.inductiveautomation.com/t/run-multiple-versions-of-custom-modules/11855/3 "2016-07-22T13:54:39Z")

</div>

why don't you create every version as a new module during trials which your customers can install and uninstall and finally select the last version as the final one.