Reputation: 1381
I use a Visual Studio 2017 Installer Project to create an MSI for my project. I also create clickonce packages because of their autoupdate
This is because I have 3 types of users;
Users that want access to the latest version - this I can make work with advanced installer
Corporate users that distribute their own updates automatically and simply
Corporate users that update using an MSI
For 2. I use the clickonce 'feature' that you can configure it so that it looks for updates in the location it was installed from. This works REALLY well for my clients that want to control their updates rather than have them automagically available from my website. I dont need to make packages for individual businesses with their specific URL, I just give them the installer and they run it from a share. When an update is accepted, they just replace it.
But I have finally kicked clickonce to the kerb. Too many times the update just decides to not work on specific machines for no decipherable reason. It is truly a horrible technology.
I am looking instead at advanced installer which appears to do everything I need - except the update from install location. Is this possible? Or do I need to configure the location in the installer. If the update URL has to be explicitly provided, can it be provided via a config file, or do I need different packages for every different update URL?
Upvotes: 1
Views: 651
Reputation: 1347
With Advanced Installer you can set the updates location at install time using data from user input. For instance you can use a property reference in "Updater" view of your project. Then at install time set the above property to the location value get from user. This way the installed Updater tool will search for updates in the location set by user at install time.
Then when delivering updates to your user network you should just instruct him to copy the updates in the location configured at install time.
Hope this helps.
Upvotes: 1