You can install the Client Framework standalone software from the installer as a standalone component on the end-user workstation.
The Client Framework standalone component includes a complete WPF Container application that hosts the Views assembly and displays a view that corresponds to a particular ispec. It also includes the AB Suite Client Framework MVC Scaffolder and the NuGet Packet Manager for Visual Studio 2017.
To install the Client Framework standalone software, perform the following:
Click Client Framework (32-bit) or Client Framework (64-bit) on the Client Environment interface. The Installation wizard appears and a number of checks are carried out on the system to ensure it has the correct underlying system software to complete a satisfactory installation.
Notes:
If two instances of the installation wizard appear, close one instance.
If the Client Framework software is already installed on your machine as a separate instance, the Program Maintenance dialog box appears; you can choose to repair or remove the Client Framework software.
If the checks are successful, a welcome dialog box appears, followed by a license dialog box. To accept the conditions and continue with the installation, click I accept the terms in the license agreement; if not, clickI do not accept the terms in the license agreement.
Accepting the license agreement allows you to select the target drive and directory for the installation, if you do not want to accept the default installation location.
Click Next to proceed with the installation.
You can click Back to make changes, if any.
At the completion of the installation, the Installation Shield Wizard Completed dialog box appears. This screen allows you to view the readme file and the Windows Installer log file. If you want to view the readme file or the Windows Installer log file, select the respective check box.
Click Finish to complete the installation.
Configuring WPF Client Container
Before running applications, you must edit the “<Client Technology Folder Name>_Config.rtxml” configuration file. For example, if the Client technology folder in System Modeler has the name “WPFClient”, the configuration file should be “WPFClient_Config.rtxml”. This file contains configuration information to enable the WPF client to find and connect to the application component. This file is automatically created during the generation of the system. The administrator might have already modified this configuration file in the installation package. Check with your administrator before proceeding to modify the file.
A default copy of the configuration file is located at <System Modeler project folder>\Access Layer API Deploy.
The following entries of the configuration file might need to be edited:
<system name> should be set to a string with the name of the system. This name appears on the title bar of the WPF client application window; for example, <system name = “Sample”>
<startupSystem name> should be set to the same string as <system name>. Note that you can have multiple <system name> sections in the configuration file. This <startupSystem name> entry specifies which system is started when you first open the WPF Client; for example, <startupSystem name=”Sample”>
<componentName> should be set to the name of the COM Program ID that the system was generated with for example, <componentName>SAMPLE</ componentName>. Contact your administrator for this value. This name is case-sensitive and must correspond to the case of the actual name of the COM Prog ID.
<runtimeServer> must contain the machine name where the runtime system was deployed and installed. Contact your administrator for this value. Use “localhost” if you generated a test system to your own machine.
<downloadServerURI> is a location where the required WPF Client assemblies are retrieved from. This can be a file share on the local or remote machine; for example, <downloadServerURI>file://C:\Users\<User Name>\Documents\Visual Studio 2017\Projects\ForwardModel\Access Layer API Deploy. It can also be an FTP or HTTP site from where you can download the assemblies.
To run the WPF Client Container, setup a shortcut that allows you to specify the name and location of the Configuration file as a parameter; for example, “<WPFClient Installation Path>\WpfClient.exe” “C:\Users\<UserName>\Documents\Visual Studio 2017\Projects\<Technology Folder>\Access Layer API Deploy\WpfClient_Config.rtxml”.