Windows Forms 2.0 Programming

19. ClickOnce Deployment So far, this book has focused on the development of Windows Forms applications. At some point, though, a Windows Forms application needs to be deployed. The traditional means for doing so is via a setup application o...

A Day in the Life of ClickOnce Deployment As a test of the ClickOnce deployment model for Windows Forms applications, I built the simple game shown in Figure 19.1[3][3] Any similarity to any other very popular game that you may already be famili...

ClickOnce Configuration The Publish Wizard is a lightweight UI wrapper that provides a quick-fire publishing option. However, the Publish Wizard hides the rich support provided by ClickOnce from VS05 that allows developers to tailor application de...

ClickOnce Security ClickOnce, as you've seen, uses the manifests of the application it's about to download to analyze the application. If there are issues in one or more of four categoriespublisher, machine access, installation, and locationthos...

Managing Permissions ClickOnce doesn't force users to elevate permissions or to download an application, but you can avoid the issue altogether by programming specifically for partial trust. This involves detecting when your assemblies require mor...

Considerations for Partially Trusted Assemblies Both the Wahoo and the WahooControlLibrary assemblies are designed to work within the restricted set of Internet permissions; this meant that it was difficult to implement the complete set of functio...

Processing Command Line Arguments One other feature you need to support in a programmatic way is command line processing. In a normal application, command line parameters are available from the string array passed to Main: static void Main(string...

Where Are We? ClickOnce deployment allows you to deploy Windows Forms applications using the same model you might be accustomed to with web applications. But more than that, ClickOnce is a highly configurable framework for packaging, publishing,...