3 ms·
I would be far more interested in how the auto-update process works rather than hearing that someone automated their build. Would be way-crazy-awesome if they c
by j_s 14y ago
I would be far more interested in how the auto-update process works rather than hearing that someone automated their build. Would be way-crazy-awesome if they could pull it out and release it open source, but they seem to be leaning on it as a pretty serious part of their secret sauce.
- HarshaThota 14y agoThey are currently using ClickOnce for the auto-update mechanism but you may find these interesting: https://github.com/github/Shimmer https://github.com/github/Shimmer https://github.com/synhershko/NAppUpdate https://github.com/synhershko/NAppUpdate
- j_s 14y agoThanks. I haven't looked at ClickOnce in a long time, interesting to hear it is a viable solution for commercial apps. For example, did not know it could update in the background for next run of the app.
- xpaulbettsx 14y agoIt really isn't, which is sad, because it's like 95% Awesome and 5% Showstopper Bugs. Here's the most damning aspect of it: if you sign your ClickOnce application (which you are required to or else ClickOnce's installer displays scary "Don't Install This" messages), then the cert expires, every user has to uninstall and reinstall. Completely untenable. http://github.com/github/shimmer http://github.com/github/shimmer is our plan for the future.
- j_s 14y agoThanks for this reminder... documenting how to cleanly transition from ClickOnce to shimmer would be a spectacular resource.
- xpaulbettsx 14y agoHere's how we do it: https://gist.github.com/3777989 https://gist.github.com/3777989 The only other "Secret Sauce" is that you have to disable checking for updates at startup in the ClickOnce settings.