In this course, we explore the capabilities of ClickOnce, with demos showing all its configuration options, the deployment API, the bootstrapper for installing prerequisites, and how to handle signing and security.
ClickOnce is one of the easiest ways to get your application installed on your client's computers, and keep it automatically updated. In this course, we explore the capabilities of ClickOnce, with demos showing all its configurations settings, the deployment API, the bootstrapper for installing prerequisites, and how to handle signing and security.
Mark Heath is a software developer based in Southampton, England, working
for NICE Systems as a software architect creating cloud based digital
evidence management systems for the police. He is the creator of NAudio, an
open source audio framework for .NET.
Introducing ClickOnce Hi, my name's Mark Heath and welcome to the Pluralsight course on ClickOnce Deployment Fundamentals. In this first module we'll be introducing what ClickOnce is and why you might want to use it. This course is designed to help you decide whether ClickOnce is the right technology for your application, and to show all the various ways that you can configure it. So in this first module we're going to start off by simply answering the question: what is ClickOnce? What type of applications can I use it for? And what are the problems that ClickOnce is designed to solve? We'll briefly discuss some of the main capabilities of ClickOnce and then we'll see it in action with a brief demo. Finally, we will discuss some limitations of ClickOnce, some scenarios in which it might not be the most appropriate choice, and so I'll mention some alternative installer options that you can use instead.
ClickOnce Updates and Data Files Hi, my name's Mark Heath and in this module we'll be looking in more detail at ClickOnce updates and how you can manage your data files. So we'll start by answering the question, where to the files that are part of my application actually end up on the installed computer? We'll see the application directory, which contains our executable and its dependencies, and we'll also see where the data directory is that we can use to store our own data files. We're also going to be looking in this module at how you can use the ClickOnce deployment API, which allows you to detect in your application that you're running as a ClickOnce application and do a number of useful things, such as downloading file groups, and also checking for and installing updates on demand. We'll also look, in a bit more detail, at the process of how you can, in your code, handle when an update has taken place. You need to be able to detect the first run of new version of your application and this will allow you to migrate data from the previous version of your application into the new version. And finally, we'll also see the support that ClickOnce has for not only uninstalling your application, but for rolling it back to a previous version. So let's get started.