


The problem comes if you try to convert the application to per-machine. For per-user applications, most vendors consider placing those setting files near the executable. Usually, you want an application to save some settings or running information in files. Important: Never change the installation type of an application unless you fully understand how it works. One mistake that we see happening very frequently is for IT Pros to convert ClickOnce applications (per-user) to per-machine applications without considering all the issues that could occur during the execution of that particular application.

This comes as no surprise since the per-machine approach makes it much easier to manage your applications in the infrastructure. So, most vendors prefer the per-machine method of deploying applications. That means that most of the applications that we find on the market today require administrative rights to be installed. In general, IT Pros are used to building MSI and EXE packages to be installed per-machine. Per-user applications are kind of difficult to repackage. What are the challenges of repackaging a ClickOnce application?ĬlickOnce shares some similarities with MSIX – the main one being that they are per-user applications. Note: If you want to learn more about repackaging, take a look at our repackaging best practices. But, what if you want to "repackage" a ClickOnce application? That's what we'll be covering in this article. In one of our previous articles, we discussed How to Replace the ClickOnce app with MSIX. ClickOnce is a Microsoft deployment technology that facilitates deploying Windows applications.
