List Of ClickOnce Articles
Here’s a quick reference to my ClickOnce articles.
Windows 8 and ClickOnce — the definitive answer explains how ClickOnce applications work on Windows 8, and what you need to do if you are deploying from the internet zone.
Host your ClickOnce deployment for pennies per month explains how much it costs to use Azure blob storage to serve up your ClickOnce deployments. It’s dirt cheap!
How to host a ClickOnce deployment in Azure blob storage explains how to use Azure blob storage to serve up your ClickOnce deployments. If you don’t have access to a server, this can be a really inexpensive way to host your ClickOnce application.
How about a bootstrapper package for SQLServer Express 2008 R2? explains how to make a bootstrapper package for the latest version of SQLServer Express to use as a prerequisite to a ClickOnce application.
How do I programmatically find the deployed files for a VSTO Add-In? explains how to write code to be used in an Office Add-In written with VSTO to access the deployment files. Hint: It’s not in the same place as the executing assembly.
MIME Types for ClickOnce deployment details the required MIME types required for the different applications you can deploy with ClickOnce, and shows you a way to define them yourself if using an Apache webserver.
Enhanced logging in ClickOnce deployment to help you diagnose installation problems.
What’s new in ClickOnce deployment in .NET 4.0 summarizes the new features available in VS2010 and .NET 4.0, and provides links to articles providing more detail.
The Future of ClickOnce Deployment talks about the continuing support from Microsoft.
How to pass arguments to an offline ClickOnce application, even if it’s deployed to a file share. This came along with the release of .NET 3.5 SP-1 (when they added file associations), and most people don’t realize you can do this now. I show you how to call a ClickOnce application and pass the arguments in different ways, and how to read and parse them in the application itself.
How to deploy the SQLServer Compact Edition software locally rather than deploying it as a prerequisite, which gives you control over the version installed and reduces the installation steps for your customer.
The published MSDN article about ClickOnce deployment and Certificate Expiration. This explains the problem that can occur when your signing certificate expires, in what cases it applies, and how to handle it. This is the updated and official version of my blog posting about this subject. This also includes how to use MakeCert to make your own certificates.
How to extend an existing certificate, even if it has expired. This explains how to use RenewCert. This is a companion article to the MSDN article on Certificate Expiration.
How to move a ClickOnce deployment from one deployment location to another.
Installing a ClickOnce application for all users (short answer: you can’t). I asked the product team about this again in February 2010, and it is completely counter to the design of ClickOnce deployment, so I wouldn’t expect to see if any time soon.
Where do I put my data to keep it safe from ClickOnce updates? This offers a solution that gives you more control over when your data is modified, and makes sure it doesn’t get lost when you publish an update to your application.
How to deploy a ClickOnce application to localhost. If you install IIS on your development computer, you can deploy your application locally and test your deployment from either your development computer, or another computer on the same network.
How to create a desktop shortcut for your ClickOnce application. This shows how to do this programmatically.
How to create a desktop shortcut for your ClickOnce VB application. This is an addition to the first article. The startup of a VB application is different from a C# application; this addresses that difference and shows VB developers how to handle it.
Microsoft Windows Updates and .NET 3.5 SP-1 How to migrate from .NET 2.0 or .NET 3.0 to .NET 3.5 SP-1, and information about the Client Framework.
How to install multiple versions of the same ClickOnce application. You would want to do this if you wanted to have both the production version of your application and a QA version installed at the same time.
ClickOnce and Expiring Certificates This is the original version. I’ve left this in for nostalgia and because it is the first post on my blog. You should read the MSDN article for the final and official version. This one is accurate, but the MSDN article is more thorough and includes .NET 4.0.