Version 5, last updated by markcopenhaver at July 18, 2010 19:35 UTC

An installer is an executable program that installs your component on the EncounterPRO-OS client computer.  This must be done silently because EncounterPRO will install the component on a computer the first time the component needs to be instantiated.  Often there is an end-user in front of the computer at that time who will not know the answer to any setup dialogs.

You should understand that EncounterPRO-OS will instantiate your component at runtime using late binding.  The assembly version is included in the instantiation so it is important that EncounterPRO-OS be able to find the correct version of your assembly at runtime.  Because the GAC handles multiple versions of the same assembly, we strongly recommend that all EncounterPRO-OS component assemblies be deployed to the GAC.

Any setup technology will work (e.g. InstallShield, WIse, etc) provided that you can create a setup program that installs your component without requiring any information from the user.  The installation of many components is as simple as adding the component assembly to the GAC, so to facilitate components with relatively simple installation needs, there is an NSIS generic installer that will build a setup program for you.  You can use this installer builder if all you need are files placed in the program directory, system directory or GAC.  The Generic installer can also register your files for COM/Interop if needed.  You can find more information about the generic installer here.

 It is highly recommended to include the EncounterPRO-OS Component Base Class assembly that was used to develop your component.  This will insure that Windows will be able to resolve assembly dependencies when EncounterPRO-OS instantiates your component.