.NET Components: On other CIMPLICITY Systems
About this task
- Component files copied to other systems.
- Components added to the component browser of another CIMPLICITY system.
Component Files Copied to Other Systems
If new components are created and inserted into CIMPLICITY screens on one CIMPLICITY system, and the saved screens are opened on another CIMPLICITY system, the screens will not load with the new components if they do not exist on the new system. This is the same situation as ActiveX controls if they are not installed (copied and registered) on a new target system.
There is no need to register the new components: neither the component assembly nor the component type library files.
Copy the same directory hierarchy relative to the ..\<CIMPLICITY Installation>/exe folder to other systems in the same hierarchy.
Example
If the ChartControls.dll, Occ.ChartControls.dll and Occ.ChartControls.tlb files are copied to the ..\ <CIMPLICITY Installation>\exe\DotNet Components\My Sample Components folder of another CIMPLICITY system, the TrendChart objects configured on the original system will then load and function on the new system.
Any custom or third-party supporting assemblies in the <CIMPLICITY Install>\exe folder must also be copied to the <CIMPLICITY Install>\exe folder of other systems.
Components Added to the Component Browser of another CIMPLICITY System
A suitable entry needs to be on the Component Browser's tree view to insert objects of a new component into a CIMPLICITY screen on another system,
Options include the following.
Keep all the created components synchronized across all systems.