We're currently using ClickOnce to deploy our Windows Form application. We're investigating the possibilities to use multiple release channels, such as Stable and Beta and the possibility to only release an update to x-number of clients.
I can't find any information indicating the ClickOnce have support for this out of the box and I'm wondering if anyone have solved this with a workaround?
This isn't exactly what you want, but it's close. It might be useful for others who look for this.
Applications only check for updates from one location, regardless of install location. I'm going to start calling this the "stable" directory.
I'm going to make another directory for beta installation.
When a beta version live test is acceptable, I'll just copy that version over to the stable directory, and all clients with a lesser version of that will update.
Users would never automatically update to a beta version, which may be a downside of this approach. To run a beta requires an installation from a beta link. And those beta user will eventually just be running the stable version unless they continually opt-in for each beta release.
