8.2.4 Deploying a Component
The .NET Framework assembly should be deployed with your Visual LANSA application using the LANSA Application Deployment Tool. For assistance in creating the deployment package see the LANSA Application Deployment Tool help guide.
This topic will concentrate on where to install the assembly on the target machine. The following lists the search order that Visual LANSA uses to locate the assembly.
1. The specified location. Whether you have specified the fully qualified path or used the registry method this is the first place that is searched. If you have used the registry entry method then you will need to create the registry entry on the deployed system. If you have used the fully qualified path then the assembly will need to be installed in the exact location on the deployed system.
2. Partition Execute directory (<sys dir>\x_<ppp>\execute), for example <LANSA Root Directory>\x_win95\x_lansa\x_<ppp>\execute.
3. System Execute directory (<sys dir>\execute), for example <LANSA Root Directory>\x_win95\x_lansa\ execute.
4. System wide generic load. Searches the Global Assembly Cache and the location of the running executable. Care should be taken when relying on this method because only the assembly name is used when searching for the assembly. Version, culture and the public key token are not specified. This means that you may inadvertently load the incorrect version of the assembly if there are other assemblies in the Global Assembly Cache with the same name.
Your .NET Framework assembly should be deployed to one of these locations.