How do I install a patch in a ClickOnce application?
I recently discovered that there is a bug in the Dutch .NET assembly that effectively destroys navigation windows on Dutch SP1 or higher. See this link for details
A hotfix is available, but how can I distribute it using a ClickOnce application? I'm terrible that this situation, which appears to have been known since February, has not been remedied. I am also puzzled: any dutch vista machine running SP1 or higher will crash on wpf nav navigation so there should be more screams in it. Does anyone not write navigation programs?
source to share
I don't think there is any way to deploy the fix as part of a ClickOnce application, as that would break the whole idea of clicking once. This should be a zero impact installation environment.
What you could do is add a section of your program that checks for the specific flaw and then opens a message box / form prompting the user to deploy the specific hot fix. Including the link should make the process pretty straightforward. Not a perfect solution, but it should help ease your specific problem.
source to share
If you've built a new deployment package and installed a "hotfix" as one of your prerequisites, you might get a result where the user needs to install the hotfix before the user installs the updated version of your application.
I tend to think, however, that the error in the .NET framework must go beyond the support requirements for ClickOnce applications. If this is an intranet application, you should probably work with your IT department to get the fix rolled out to your users as a separate effort.
However, if your ClickOnce application is online, then either the JaredPar suggestion (a check / dialog inside your application to see if the fix is installed or not) or just a notification on your site with links to the fix should be sufficient.
source to share
Good luck, I recently learned that ClickOnce web applications suck.
We are also looking for a better way to fix the ClickOnce application. It currently takes up almost 30MB in size :(
I am currently considering using bsdiff in a deployed CDROM application, fixing the install sources, possibly supporting only minor updates (e.g. 1.0.1 - 1.0.2).
There are still many potential problems.
source to share