Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

How do I deploy a solution to multiple workstations that have different locations for the same application?

Updated on February 13, 2017

When deploying a Studio solution to multiple workstations and one or more of the workstations has the target applications installed to a different path (disk location) than the machine on which the solution was developed and deployed, users sometimes unnecessarily create and deploy separate solutions to accommodate the various target application paths (locations).

There are several ways to handle this situation:

  • If the path to the application is set in the Windows System Path (Windows Environment Variables) for all workstations, then you are not required enter the path to the target application in the adapter properties. Rather, you can set the target application adapter ResolvePath property to False and the system will resolve the application path using the Windows environment variable.
  • Add Configuration project items to your solution equal to the number of target application paths you need to support. The Project Configuration feature lets you set parameters that enable different versions of a project to be saved and deployed to Runtime workstations, without creating multiple projects. Set the Configuration properties to match the various paths. Then when you create the project deployment files, select the option to Deploy Project with All Configurations. This will create a separate deployment package for each configuration (or path in this case).

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us