Click-Once Deployment
-
Couldn't exactly decide where to put this, hope this is okay. From what I have seen, in order to use click-once the application must be installed via a click-once installer. Even if everything has been setup for click-once, installing via the MSI seems to leave behind the auto-update bootstrap. I understand that installing via click-once is comparable to running the app in a sandbox, ect ect. What I would like to do, is have the user install the application via MSI (so that I may make registry changes and the like... just for the sake of argument assume that I MUST install via MSI). But I would like to leverage the auto-update functionality of click-once. Is there any way to combine the two? Visual Studio 2005 Team Edition, C#
-
Couldn't exactly decide where to put this, hope this is okay. From what I have seen, in order to use click-once the application must be installed via a click-once installer. Even if everything has been setup for click-once, installing via the MSI seems to leave behind the auto-update bootstrap. I understand that installing via click-once is comparable to running the app in a sandbox, ect ect. What I would like to do, is have the user install the application via MSI (so that I may make registry changes and the like... just for the sake of argument assume that I MUST install via MSI). But I would like to leverage the auto-update functionality of click-once. Is there any way to combine the two? Visual Studio 2005 Team Edition, C#
Try this How to: Check for Application Updates Programmatically Using the ClickOnce Deployment API[^]
only two letters away from being an asset
-
Try this How to: Check for Application Updates Programmatically Using the ClickOnce Deployment API[^]
only two letters away from being an asset
Thanks for that. As far as I can tell that still doesn't use an MSI file to perform the installation. I have been searching around for more information all day and I think the official answer is click-once and MSI don't play ball. But just to confuse matters a little, it does seem that a VSTO add-in does exactly what I want. Installs via a MSI and updates itself via clickonce
-
Thanks for that. As far as I can tell that still doesn't use an MSI file to perform the installation. I have been searching around for more information all day and I think the official answer is click-once and MSI don't play ball. But just to confuse matters a little, it does seem that a VSTO add-in does exactly what I want. Installs via a MSI and updates itself via clickonce
You may want to look up Application Updater Block, that may be more of what you need.
only two letters away from being an asset
-
Couldn't exactly decide where to put this, hope this is okay. From what I have seen, in order to use click-once the application must be installed via a click-once installer. Even if everything has been setup for click-once, installing via the MSI seems to leave behind the auto-update bootstrap. I understand that installing via click-once is comparable to running the app in a sandbox, ect ect. What I would like to do, is have the user install the application via MSI (so that I may make registry changes and the like... just for the sake of argument assume that I MUST install via MSI). But I would like to leverage the auto-update functionality of click-once. Is there any way to combine the two? Visual Studio 2005 Team Edition, C#
newkie, when you build your ClickOnce app, you typically deploy it with a prerequisites package (a .MSI file) that installs any prerequisites, modifies the registry, the GAC, whatever. To make this part of your prerequisites, you must bootstrap it and make it a prerequisite of your ClickOnce deployment. There's a tool (deployed via ClickOnce) that can generate Visual Studio BootStrap packages for you; all you do is point it to your MSI file, and it will generate it. That application can be installed here[^]. Once you've built a bootstrap for you .MSI file, go into Visual Studio, open up the properties of your ClickOnce project, go into the Publish tab, click the Prerequisites button. Now, your newly created bootstrapper for your MSI package will show up in the checklist. Check it. Now deploy your app via click once. It will generate a webpage that lists prerequisites (it will list your MSI file now), and the page will have a link to Install prerequisites, or launch the application. If you click Install, it will check for any needed prerequisites (.NET framework, your .MSI file, and any others you've specified) and install those on-demand. It's very cool. :cool:
Tech, life, family, faith: Give me a visit. I'm currently blogging about: For Christians: The Significance of Yom Teruah The apostle Paul, modernly speaking: Epistles of Paul Judah Himango