Deploying Separate User/Site Configurations with ClickOnce

Microsoft's ClickOnce framework is a powerful tool for deploying and updating Windows forms applications. Learn how to deploy separate application configurations via two methods: installing and updating from different locations, and using URL parameters.

ClickOnce in .NET is a technology that allows you to marry the rich user experience of Windows Forms applications with the deployment and update advantages of Web applications. What do you do, however, when you want to deploy different application configurations to different sets of users? For example, you might have a Power User version of the application to be distributed to a set of users who require advanced features and a normal version of the application to be distributed to a set of users who only require basic features. you will learn two different methods for distributing different application configurations to users.



Method 1: Installing and Updating from Different Locations



The first method for deploying different configurations via ClickOnce is to set up separate installations for each configuration of the application and pointing all versions of the application to one, common update location. This method can cause quite a bit of maintenance overhead because you have to maintain a different installation for each configuration that you have. However, once you set up the installations, you can streamline the process of deploying updates because all of the applications (regardless of the original installation location) will update from the same place while maintaining the initial configurations.

To follow the demonstration below, you will need to set up the following:




  • Create the folder "C:\Temp\ClickOncePublishFolder"

  • Create the folder "C:\ClickOnceInstallationPath"

  • Create the folder "C:\ClickOnceUpdatePath"

  • Configure "ClickOnceInstallationPath" to be a shared folder with the same name

  • Configure "ClickOnceUpdatePath" with IIS to be a virtual directory with the same name



Read the Rest of this Article at Developer.com

Regional Articles
- Deploying Separate User/Site Configurations with ClickOnce Alabama
- Deploying Separate User/Site Configurations with ClickOnce Alaska
- Deploying Separate User/Site Configurations with ClickOnce Arizona
- Deploying Separate User/Site Configurations with ClickOnce Arkansas
- Deploying Separate User/Site Configurations with ClickOnce California
- Deploying Separate User/Site Configurations with ClickOnce Colorado
- Deploying Separate User/Site Configurations with ClickOnce Connecticut
- Deploying Separate User/Site Configurations with ClickOnce DC
- Deploying Separate User/Site Configurations with ClickOnce Delaware
- Deploying Separate User/Site Configurations with ClickOnce Florida
- Deploying Separate User/Site Configurations with ClickOnce Georgia
- Deploying Separate User/Site Configurations with ClickOnce Hawaii
- Deploying Separate User/Site Configurations with ClickOnce Idaho
- Deploying Separate User/Site Configurations with ClickOnce Illinois
- Deploying Separate User/Site Configurations with ClickOnce Indiana
- Deploying Separate User/Site Configurations with ClickOnce Iowa
- Deploying Separate User/Site Configurations with ClickOnce Kansas
- Deploying Separate User/Site Configurations with ClickOnce Kentucky
- Deploying Separate User/Site Configurations with ClickOnce Louisiana
- Deploying Separate User/Site Configurations with ClickOnce Maine
- Deploying Separate User/Site Configurations with ClickOnce Maryland
- Deploying Separate User/Site Configurations with ClickOnce Massachusetts
- Deploying Separate User/Site Configurations with ClickOnce Michigan
- Deploying Separate User/Site Configurations with ClickOnce Minnesota
- Deploying Separate User/Site Configurations with ClickOnce Mississippi
- Deploying Separate User/Site Configurations with ClickOnce Missouri
- Deploying Separate User/Site Configurations with ClickOnce Montana
- Deploying Separate User/Site Configurations with ClickOnce Nebraska
- Deploying Separate User/Site Configurations with ClickOnce Nevada
- Deploying Separate User/Site Configurations with ClickOnce New Hampshire
- Deploying Separate User/Site Configurations with ClickOnce New Jersey
- Deploying Separate User/Site Configurations with ClickOnce New Mexico
- Deploying Separate User/Site Configurations with ClickOnce New York
- Deploying Separate User/Site Configurations with ClickOnce North Carolina
- Deploying Separate User/Site Configurations with ClickOnce North Dakota
- Deploying Separate User/Site Configurations with ClickOnce Ohio
- Deploying Separate User/Site Configurations with ClickOnce Oklahoma
- Deploying Separate User/Site Configurations with ClickOnce Oregon
- Deploying Separate User/Site Configurations with ClickOnce Pennsylvania
- Deploying Separate User/Site Configurations with ClickOnce Rhode Island
- Deploying Separate User/Site Configurations with ClickOnce South Carolina
- Deploying Separate User/Site Configurations with ClickOnce South Dakota
- Deploying Separate User/Site Configurations with ClickOnce Tennessee
- Deploying Separate User/Site Configurations with ClickOnce Texas
- Deploying Separate User/Site Configurations with ClickOnce Utah
- Deploying Separate User/Site Configurations with ClickOnce Vermont
- Deploying Separate User/Site Configurations with ClickOnce Virginia
- Deploying Separate User/Site Configurations with ClickOnce Washington
- Deploying Separate User/Site Configurations with ClickOnce West Virginia
- Deploying Separate User/Site Configurations with ClickOnce Wisconsin
- Deploying Separate User/Site Configurations with ClickOnce Wyoming

Rss   Delicious   Digg   Add To My Yahoo   Add To My Google   Bookmark   Search Plugin

Topics:
Architecture & Design Languages & Tools Project Management Web Services
Database Microsoft & .NET Security Wireless
Java Open Source Techniques XML