Project Deployment Dialog

Use the Project Deployment Dialog to create Studio project deployment files for use with Runtime/Agile Desktop. This dialog lets you configure and create deployment packages. Note that the Project Properties - Application, Build, and Deployment are applied when creating the deployment package. For more information, see Project Properties.

The Project Deployment dialog contains these main parts:

See the following table for definitions of the Project Deployment fields and tabs.


Project Deployment Dialog



Project Name

Shows the name of project as it is displayed in Solution Explorer.

Deployment Version

Shows the current deployed version. For more information, see Project Properties.

Deploy to


Full path where the deployment package for the project will be located. Usually, this is an interim location on the designer computer from which the files are copied to a distribution location. The distribution location must be accessible to the Runtime workstations. You have several options for distributing deployment packages:

  • Web Server distribution – Using this method, the deployed solution package is saved to a webpage that can be accessed by the Runtime desktops/users. For more information, see Web Server Distribution.

  • File Share distribution – Using this method, the deployed solution package is saved to a network share that can be accessed by the Runtime desktops/users. For more information, see File Share Distribution.

  • Local System Deployment – Using this method, the deployed solution package is copied to each Runtime user’s workstation. For more information, see Local Folder Distribution.

Signing Certificate

Click Browse to select a certificate. The Select Certificate window is displayed where you can specify the store location, the store name, and the certificate. Complete the Select Certificate dialog as follows.

  • Store Location – Select account for the associated certificate - Current User or Local Machine. The Current User store location is associated with a particular user while the Local Machine store location is associated with the computer. Any user can request certificates and have these stored in their Current User store location. For Local Machine store locations, you must have administrative rights to place certificates in that store location. In general, the Local Machine store location is used for the storage of certificates which apply to the computer or on a system-wide basis and are not tied to a specific user.

  • Store Name – Select the store name for the certificate. The store name is a physical or logical folder. A default Windows installation will include various commonly used store names, such as Personal, Trusted Root Certification Authorities, Enterprise Trust, and so on.

  • Certificate – After specifying the Certificate Store (Location and Name), click Browse next to this box to open the Signer Certificate window. This dialog lists all signer certificates for the Certificate Store. Highlight the signer certificate you want to use for the deployment package and click OK. The name of the certificate is displayed in the Certificate box.

Click OK in the Select Certificate dialog to use the certificate in the deployment. To remove the certificate, click Clear in the Select Certificate window.

Publish to OpenSpan Server

Check this box if Studio is configured to communicate with the Deployment Portal (formerly known as Management Console) and you want to deploy packages via the Deployment Portal.

Additional References Tab


Lists the assembly files for any references added to the deployed project. For example, if you are deploying a Studio project that references another Studio project, the name of the referenced project's assembly file displays here. For more information, see Using Project References.

Translators Tab


Lists all translator assembly files associated with the project. Translators assemblies are used by the system to integrate with specific technologies, such as .NET.

Additional Files Ta


Displays the names (including paths) of files added to the deployment package, such as text documents, PDF files, and custom built components. To add files to the deployment package, use the Miscellaneous Files property on the Project Property - Application page. For more information, see Project Properties.


Privacy | Trademarks | Terms of Use | Feedback

Updated: 18 June 2020

© 2016 - 2020 Pegasystems Inc.  Cambridge, MA All rights reserved.


OpenSpan data classification label