Smartclient Deployment: Deploying to users

 

Once you have created a deployment package, the next step is getting your application to your end users.

 

CREATING A DEPLOYMENT PACKAGE  >  DEPLOYING TO END USERS  >  DEPLOYING UPDATES  >  ADVANCED DEPLOYMENT OPTIONS

Making your installation files available to end users

The deployment tool produces a set of installation files which must be manually copied from the Build Folder (this is the folder where the build process will output your package) to the Client Update Location folder (this is the location that your end users will need to install and update from).

Each deployment package contains a setup.exe file, which when run, will install the applications you have included in your deployment package (typically this will be a Newlook Smartclient or Smartframe application but it can also include other executables as well). The deployment package also consists of a RELEASES file, one or more .nupkg files and (if you have selected the option to create it), a setup.msi file.

Once installed, the deployed application has an in-built tool which checks for updates at the Client Update Location and can automatically install them, depending on the update mode you have specified when you created the deployment package. There is no need to redistribute a setup file to end users when an update is introduced. In order for this update tool to work correctly however, the location where you store your installation package files must match exactly the location specified in the package's Client Update Location.

Client Update Location options

There are three types of locations you can copy an installation package to. Which type you choose will depend on your specific requirements:

  1. Web. The installation package is stored on a machine hosting a website (web server) accessible through HTTP. This scenario is perfect for an environment where end users can access resources via the web. In this scenario the Client Update Location will be prefixed with http:// or https://. Microsoft IIS is the only currently supported Web Server.
  2. Shared network folder. The installation package is stored on a single machine that is accessible by other machines within a network with the same unique address. This scenario is ideal in an environment where multiple end users have their own machines and each machine has access to the machine on which the installation package is stored.
  3. Local folder. The installation package is copied to a different folder on the same machine that the package is created on. This scenario may be an option in an environment where multiple end users share the user of a single machine or for a developer who wishes to test deployment locally.
    IMPORTANT:

    If you are using a web or shared network folder, you will need to manually copy all the files in your Build Folder (use theGo To Folder button to quickly open the location) to the location specified in the Client Update Location for the package (use the link in the Results log to quickly open this location). If you are using a local location, the files will automatically be copied from the Build Folder to the Client Update location.

When an end user downloads and runs setup.exe for the first time, the contents of your deployment package (which include all your solution files plus any files required to run Newlook Smartclient) will be installed on their machine in the folder C:\%UserProfile%\Local\. Once complete, the user will receive notification that the installation was successful, and any shortcuts that you configured in the deployment package will be available on their desktop.

Next step: Deploying updates

See Also

Creating a deployment package | Deploying updates | Signing your deployment | Deployment Reference

© 2004-2021 looksoftware. All rights reserved.