Installation softwares (PC desktop)
-
I use Inno Setup which is quite easy to use. Not sure how well it would integrate into an automated process.
I second the motion for InnoSetup! I would recommend it over any of the other tools because it is a lot easier to use. I've used InstallShield, InsallShieldLE, and the old (VStudio 2008 and before) built-in package creator (whatever that thing was) and InnoSetup is consistently the best, easiest and most reliable. You can learn it quickly and it consistently works. However, the one issue is that InnoSetup cannot generate an MSI. Sometimes that is a problem.
-
Once in a while we start having a discussion on how to improve our workflow when creating installers for our software (large, but non complex installer) We are using InstallShield; it is a beast, it works, but hard to use and integrate into our Continuous Integration tools; but it has all the features we need (EXE, redistributables, chained MSI...) Someone always ask if there is something better that we can use; so I go on the internets and look around and go to this [Wikipedia](https://en.wikipedia.org/wiki/List\_of\_installation\_software) page. I'm always surprised at how few installer software there are. I'm surprised that even Microsoft does not offer a good packaging tool. What are you using to package your software? Are we stuck on what we have right now ?
I'd rather be phishing!
I use Advanced Installer[^]. Its project file is plain text and can therefore be maintained under version control. The installer creation is command line driven, allowing you to integrate it into your CI process[^]. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Once in a while we start having a discussion on how to improve our workflow when creating installers for our software (large, but non complex installer) We are using InstallShield; it is a beast, it works, but hard to use and integrate into our Continuous Integration tools; but it has all the features we need (EXE, redistributables, chained MSI...) Someone always ask if there is something better that we can use; so I go on the internets and look around and go to this [Wikipedia](https://en.wikipedia.org/wiki/List\_of\_installation\_software) page. I'm always surprised at how few installer software there are. I'm surprised that even Microsoft does not offer a good packaging tool. What are you using to package your software? Are we stuck on what we have right now ?
I'd rather be phishing!
Inno Setup for me too, also developed a "web-updater" in C#, but it is hard to convince my colleagues to use it (bit of a learning curve). Some alternatives can be found here: https://www.slant.co/topics/4794/~installers-for-windows-programs[^]
-
Once in a while we start having a discussion on how to improve our workflow when creating installers for our software (large, but non complex installer) We are using InstallShield; it is a beast, it works, but hard to use and integrate into our Continuous Integration tools; but it has all the features we need (EXE, redistributables, chained MSI...) Someone always ask if there is something better that we can use; so I go on the internets and look around and go to this [Wikipedia](https://en.wikipedia.org/wiki/List\_of\_installation\_software) page. I'm always surprised at how few installer software there are. I'm surprised that even Microsoft does not offer a good packaging tool. What are you using to package your software? Are we stuck on what we have right now ?
I'd rather be phishing!
We use WIX[^]. Albeit it could be tedious to write the xml installer creation scripts by hand, it fits better in an automated workflow where the said scripts are generated by higher level software ... Haven't tried to use it in the more complex scenarios (like the ones mentioned in OP) though ...
Find more in V-NET: connects your resources anywhere[^].
-
Once in a while we start having a discussion on how to improve our workflow when creating installers for our software (large, but non complex installer) We are using InstallShield; it is a beast, it works, but hard to use and integrate into our Continuous Integration tools; but it has all the features we need (EXE, redistributables, chained MSI...) Someone always ask if there is something better that we can use; so I go on the internets and look around and go to this [Wikipedia](https://en.wikipedia.org/wiki/List\_of\_installation\_software) page. I'm always surprised at how few installer software there are. I'm surprised that even Microsoft does not offer a good packaging tool. What are you using to package your software? Are we stuck on what we have right now ?
I'd rather be phishing!
I second WIX, it is a bit tedious. It works on a small install don't know about a complex one.
Got my site back up after my time in the woods! JaxCoder.com
-
I second WIX, it is a bit tedious. It works on a small install don't know about a complex one.
Got my site back up after my time in the woods! JaxCoder.com
I looked at WiX; It might work for a simple installation, but for a large installation (23,000 files) it will be hard to maintain; at least create the first iteration, adding add the components/features/files.
I'd rather be phishing!
-
We use WIX[^]. Albeit it could be tedious to write the xml installer creation scripts by hand, it fits better in an automated workflow where the said scripts are generated by higher level software ... Haven't tried to use it in the more complex scenarios (like the ones mentioned in OP) though ...
Find more in V-NET: connects your resources anywhere[^].
Yep. Creating the first iteration of the installation project is hard, in our case, for over 23,000 files it is a burden.
I'd rather be phishing!
-
Once in a while we start having a discussion on how to improve our workflow when creating installers for our software (large, but non complex installer) We are using InstallShield; it is a beast, it works, but hard to use and integrate into our Continuous Integration tools; but it has all the features we need (EXE, redistributables, chained MSI...) Someone always ask if there is something better that we can use; so I go on the internets and look around and go to this [Wikipedia](https://en.wikipedia.org/wiki/List\_of\_installation\_software) page. I'm always surprised at how few installer software there are. I'm surprised that even Microsoft does not offer a good packaging tool. What are you using to package your software? Are we stuck on what we have right now ?
I'd rather be phishing!
Installed the VS 2019 preview and noticed it has a 'built in' installer project type (Setup Project) - just poking at it now as your post reminded me of it. Had played with WIX VS plugin and was intending to use that (for what is a pretty simple install) but must say I get a little confused by some of the WIX dialog specifications/properties. This new thing might be worth a look. [EDIT] My bad - old news - and judging by the font on the dialogs this goes back a ways in some form or another. dang. [/EDIT]
-
Installed the VS 2019 preview and noticed it has a 'built in' installer project type (Setup Project) - just poking at it now as your post reminded me of it. Had played with WIX VS plugin and was intending to use that (for what is a pretty simple install) but must say I get a little confused by some of the WIX dialog specifications/properties. This new thing might be worth a look. [EDIT] My bad - old news - and judging by the font on the dialogs this goes back a ways in some form or another. dang. [/EDIT]
Tim Deveaux wrote:
Installed the VS 2019 preview and noticed it has a 'built in' installer project type (Setup Project)
Didn't it always? I'm pretty sure that a setup maker was in VS as far back as VS3 or VS4 -- but it didn't work as well as inno setup, so I stopped using it, and never looked for it again (so maybe they took it out and have put it back).
I wanna be a eunuchs developer! Pass me a bread knife!
-
I looked at WiX; It might work for a simple installation, but for a large installation (23,000 files) it will be hard to maintain; at least create the first iteration, adding add the components/features/files.
I'd rather be phishing!
Kinda thought that would be the case.
Got my site back up after my time in the woods! JaxCoder.com
-
Tim Deveaux wrote:
Installed the VS 2019 preview and noticed it has a 'built in' installer project type (Setup Project)
Didn't it always? I'm pretty sure that a setup maker was in VS as far back as VS3 or VS4 -- but it didn't work as well as inno setup, so I stopped using it, and never looked for it again (so maybe they took it out and have put it back).
I wanna be a eunuchs developer! Pass me a bread knife!
You could be right - wondered about that - I hadn't seen it though. [Edit] I think you're right - but weren't those extensions Installshield trojans? :| [/edit]
-
You could be right - wondered about that - I hadn't seen it though. [Edit] I think you're right - but weren't those extensions Installshield trojans? :| [/edit]
Tim Deveaux wrote:
weren't those extensions Installshield trojans?
Could be. I do remember people complaining about something like that (but I've read so many complaints about so many products, on the Interwebs, that it's tricky to remember which was about what). And as I say, as soon as I saw how easy (and logical) it was to knock up a script with inno, I never even thought about the built-in one again.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Tim Deveaux wrote:
weren't those extensions Installshield trojans?
Could be. I do remember people complaining about something like that (but I've read so many complaints about so many products, on the Interwebs, that it's tricky to remember which was about what). And as I say, as soon as I saw how easy (and logical) it was to knock up a script with inno, I never even thought about the built-in one again.
I wanna be a eunuchs developer! Pass me a bread knife!
But no msi, right? hmmm...
-
Once in a while we start having a discussion on how to improve our workflow when creating installers for our software (large, but non complex installer) We are using InstallShield; it is a beast, it works, but hard to use and integrate into our Continuous Integration tools; but it has all the features we need (EXE, redistributables, chained MSI...) Someone always ask if there is something better that we can use; so I go on the internets and look around and go to this [Wikipedia](https://en.wikipedia.org/wiki/List\_of\_installation\_software) page. I'm always surprised at how few installer software there are. I'm surprised that even Microsoft does not offer a good packaging tool. What are you using to package your software? Are we stuck on what we have right now ?
I'd rather be phishing!
Maximilien wrote:
What are you using to package your software?
Back when I was doing that sort of thing, I used Wise. It was easy to use and did the job. Not an option these days.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
-
Once in a while we start having a discussion on how to improve our workflow when creating installers for our software (large, but non complex installer) We are using InstallShield; it is a beast, it works, but hard to use and integrate into our Continuous Integration tools; but it has all the features we need (EXE, redistributables, chained MSI...) Someone always ask if there is something better that we can use; so I go on the internets and look around and go to this [Wikipedia](https://en.wikipedia.org/wiki/List\_of\_installation\_software) page. I'm always surprised at how few installer software there are. I'm surprised that even Microsoft does not offer a good packaging tool. What are you using to package your software? Are we stuck on what we have right now ?
I'd rather be phishing!
Have anyone used WixSharp? I've used it only once on a small project and it was simple to use. But I cannot say anything more.
-
Once in a while we start having a discussion on how to improve our workflow when creating installers for our software (large, but non complex installer) We are using InstallShield; it is a beast, it works, but hard to use and integrate into our Continuous Integration tools; but it has all the features we need (EXE, redistributables, chained MSI...) Someone always ask if there is something better that we can use; so I go on the internets and look around and go to this [Wikipedia](https://en.wikipedia.org/wiki/List\_of\_installation\_software) page. I'm always surprised at how few installer software there are. I'm surprised that even Microsoft does not offer a good packaging tool. What are you using to package your software? Are we stuck on what we have right now ?
I'd rather be phishing!
Using Ghost Installer myself. Dunno if it's THE BEST EVA, but it works. There's also ClickOnce (which is actually what MS offers, that's integrated into Visual Studio).
-
I looked at WiX; It might work for a simple installation, but for a large installation (23,000 files) it will be hard to maintain; at least create the first iteration, adding add the components/features/files.
I'd rather be phishing!
-
Maximilien wrote:
What are you using to package your software?
Back when I was doing that sort of thing, I used Wise. It was easy to use and did the job. Not an option these days.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
Yes Wise was the easiest and best of the bunch to use. Plus it could be run on the command line (batch file). Wonder whatever happened to it? Thought - Perhaps when a product is no longer supported commercially it should be legally put into the public domain, rather than leaving users high and dry?
-
Once in a while we start having a discussion on how to improve our workflow when creating installers for our software (large, but non complex installer) We are using InstallShield; it is a beast, it works, but hard to use and integrate into our Continuous Integration tools; but it has all the features we need (EXE, redistributables, chained MSI...) Someone always ask if there is something better that we can use; so I go on the internets and look around and go to this [Wikipedia](https://en.wikipedia.org/wiki/List\_of\_installation\_software) page. I'm always surprised at how few installer software there are. I'm surprised that even Microsoft does not offer a good packaging tool. What are you using to package your software? Are we stuck on what we have right now ?
I'd rather be phishing!
Yet another vote for Inno Setup[^]. Basic setups are handled using the built-in facilities, starting from a text file script. It includes competent scripting support based on Pascal. For really heavy lifting you can call out to DLL's. Scripts can be compiled from the command line. It receives pretty steady support from its author. As others have mentioned, Inno Setup's only lack is that it doesn't support MSI. For my money, that's a benefit. MSI and the Windows Installer are over-engineered and poorly documented and supported for the task they are meant to accomplish. Most of the installer-building apps based around MSI are just expensive lipstick on a pig. You mentioned you're using InstallShield. Be advised that they are #2 on my list of development teams first-against-the-wall-when-the-revolution-comes. We bought their 'international' edition for over $1K a little over ten years ago after the salesperson told us that it supported most European languages, along with Japanese, Korean, and Chinese. Come to find out, the international edition only supports English. You had to pay an additional $500 for each language you wanted to localize your install to. We chucked those ripoff fuckers and went with Inno Setup.
Software Zen:
delete this; -
I use Advanced Installer[^]. Its project file is plain text and can therefore be maintained under version control. The installer creation is command line driven, allowing you to integrate it into your CI process[^]. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
InnoSetup has all of these advantages and you can write custom install steps (in Pascal, but still, it's doable). In addition, there are multiple ways to interact with the file, from plain-old-text editor to the Inno editor, to a wizard & something with property panes and all that if you're not a coder.