That's not complicated for Windows dev. Windows devs are used to a bunch of configuration, because they grew up with it. Besides, those steps are easy to follow, and can be done quickly.
Setting environment variables is as easy as writing a .cmd file that sets them for you.
Most devs have Python installed.
Installing Scons is easy.
A paid version of VS can be easily pirated if you don't feel like paying for it. This isn't by accident: MS would rather you be writing Windows software than non-Windows software. And if you're writing software to sell, then a license isn't costly: https://www.google.com/shopping/product/7152061321388788226
"Now, a year later, do you have any updates to share regarding your experience with Omaha?"
"The update system is still running well with no required maintenance for the past year. The server gets almost a request a second at peak times... Omaha checks for updates every 5 hours. If the version that the client has doesn't match what is published it sends a URL (hosted by Rackspace) of the updater. Omaha downloads, verifies, and runs the updater."
So, there's an upfront initial time investment to get it running, and then you don't have to touch it and it still works a year later.
God we went down a rabbit hole trying to get omaha working last year. It is seriously complex. It's much-needed though, as Windows Installers are perhaps the most fucked things in existence. I am perhaps more excited for Github's Squirrel (was Shimmer), which has an awesome team behind it and notes simplicity as a priority.
I just looked into this, but it was ridiculously complex.
I just went for a Wix installer instead that installed cygwin cron as a service. The cron job then rsyncs the current version into the install dir every 5 hours. Finito.
Looks pretty cool, especially autoupdate. I'm going to take a closer look at this. AFAIK, MS has dropped support for installshield LE in VS 2013 leaving developers with the choice of buying installshield, using NSIS, or cobbling together something with ORCA, if that is even possible. Deployment is definitely the biggest pain point in windows development.
It's pretty slow at checking for new versions, though. I get the impression that's because of the way they seem to scan your disk (it seems to be a brute force "scan every directory on the disk looking for .exe files"). Also, it's fairly common for it to flag your version as out of date and then be unable to automatically update it (although it provides you a handy link to either fetch the setup your self).
That said, it's handy to have a centralised point to check for updates.
[+] [-] kijin|12 years ago|reply
Just in order to use Omaha, you need:
- A non-Express (i.e. paid) version of Visual Studio
- Python
- Scons
- Set a bunch of environment variables, because who needs configuration files?
[+] [-] voltagex_|12 years ago|reply
[+] [-] kevingadd|12 years ago|reply
[+] [-] sillysaurus3|12 years ago|reply
Setting environment variables is as easy as writing a .cmd file that sets them for you.
Most devs have Python installed.
Installing Scons is easy.
A paid version of VS can be easily pirated if you don't feel like paying for it. This isn't by accident: MS would rather you be writing Windows software than non-Windows software. And if you're writing software to sell, then a license isn't costly: https://www.google.com/shopping/product/7152061321388788226
[+] [-] damian2000|12 years ago|reply
[+] [-] sillysaurus3|12 years ago|reply
"Now, a year later, do you have any updates to share regarding your experience with Omaha?"
"The update system is still running well with no required maintenance for the past year. The server gets almost a request a second at peak times... Omaha checks for updates every 5 hours. If the version that the client has doesn't match what is published it sends a URL (hosted by Rackspace) of the updater. Omaha downloads, verifies, and runs the updater."
So, there's an upfront initial time investment to get it running, and then you don't have to touch it and it still works a year later.
[+] [-] jbk|12 years ago|reply
Apache2 makes it incompatible with GPLv2. I guess I'll skip that for VLC...
A contrario, the crash reporter, Google-breakpad, is under a BSD license.
[+] [-] pea|12 years ago|reply
[+] [-] mdpm|12 years ago|reply
[+] [-] rainmaking|12 years ago|reply
I just went for a Wix installer instead that installed cygwin cron as a service. The cron job then rsyncs the current version into the install dir every 5 hours. Finito.
[+] [-] Hominem|12 years ago|reply
[+] [-] Rafert|12 years ago|reply
[1]: http://dev.chromium.org/developers/design-documents/software...
[+] [-] veidelis|12 years ago|reply
[+] [-] mimog|12 years ago|reply
[+] [-] phireal|12 years ago|reply
That said, it's handy to have a centralised point to check for updates.
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] jonemo|12 years ago|reply
[+] [-] adamnemecek|12 years ago|reply
[+] [-] plorg|12 years ago|reply
[+] [-] caiob|12 years ago|reply
[+] [-] RachelF|12 years ago|reply
[+] [-] robodale|12 years ago|reply
[+] [-] thejosh|12 years ago|reply
[+] [-] will_hughes|12 years ago|reply
It's a completely different tangent to actually creating/managing the install process for a piece of software though.
[+] [-] psychotik|12 years ago|reply
[+] [-] unknown|12 years ago|reply
[deleted]