Timeline for Self-updating application - philosophy
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 20, 2011 at 16:44 | vote | accept | Shannon Davis | ||
| Apr 20, 2011 at 16:40 | comment | added | Shannon Davis | LOVE this answer and I am putting it in my back-pocket (for now, the "Itunes" style download has found broad appeal for cost-savings reasons.) | |
| Apr 18, 2011 at 11:56 | comment | added | Bacon Bits | @Cosmin if you don't wish to use %appdata% you could use %ProgramData% to store the downloaded files. A more philosophically correct way would be to store the archive there, then elevate to install the next time the program is run. | |
| Apr 18, 2011 at 10:11 | comment | added | user23272 | I like this approach too. The downside is that it works only for per-user installations which don't require elevation. Once you have an elevation prompt, it doesn't really matter if you need a couple more clicks to perform the update (it's not silent anymore). | |
| Apr 16, 2011 at 13:04 | comment | added | Ingo | +1 for pointing out Googles good behavior. The contrast is Adobe Acrobat Reader who as every 2nd day some apparently urgent patches to install, and disturbs one continually in one's work. | |
| Apr 16, 2011 at 6:11 | history | answered | Bacon Bits | CC BY-SA 3.0 |