Deploy the IDE Extension assemblies

IDE extensions must be deployed to the following predefined IDE folder. “[App Server Installation Path]\ArchestrA\Framework\Bin\IDEExtensions”

Remember IDE extension deployment is for the IDE node, not the GR node. Meaning, if two different IDE’s are connected to the same GR from two different machines and one of them has a newly added IDE extension then the IDE sessions from that machine would see this new extension, but the IDE sessions from the other machines would continue to see the old extensions.

When an IDE extension is composed of multiple .Net assemblies, the main assembly containing the embedded manifest (explained in the section “Getting Started with IDE Extensions”), must go to the “IDEExtensions” folder. Other assemblies belonging to the IDE extension can be installed in any folder under IDE application path, “[App Server Installation Path]\ArchestrA\Framework\Bin” or in the Global Assembly Cache (GAC).

When a developer is ready to test his IDE extension, he can just copy the extension .Net assembly to the “IDEExtensions” folder and restart the IDE. This could be iterative process to get the exact expected behavior. When the IDE extension is ready for delivery, it should be packaged into a MSI merge module, which in turn can be absorbed either into the App Server MSI install or another MSI install that checks whether IDE is installed on the machine at install time.