Skip to main content

Teamwork

Sharing Plugins Within a Team​

When working in a team environment, all members must have the plugins installed — even those who do not intend to use the toolset. This ensures that all the required plugin classes are available to every user.

If you are using source control (such as Perforce or Git) and have access to the plugin source code, the most efficient method is to install the plugin directly into the project's Plugins folder and submit it to your repository.

Licensing​
  • Team members who do not need to use the tools do not need to enter a license key.
  • If all members do have license keys entered, they can avoid consuming a seat by simply not entering the plugin's Editor mode. We also provide a mechanism to prevent accidental seat acquisition.
  • You can also provide the license key for all the team mebers by saving the key in a file in the plugin directory and submitting it to the repository.
Plugin Binaries​

If you do not store plugin binaries in your repository (you compile them on the build machine or developers compile them on their machines), you must add an exception in your .p4ignore or .gitignore file for errant_internals.dll and other files located in \Source\Errant[..]Utilities\ErrantUtilities\Internals. These specific binaries are only provided in precompiled form, so they must be submitted to the repository.