.Net setup vs InstallShield

Jan Montano

19y3k

Currently, we're in need of deciding quickly if we'll be using .net setup or installshield. In my previous company, we used installshield (9 or 10, can't remember) but I did not bother asking why, and what is really the advantage of using installshield instead of the built-in setup project for .net.

Currenly, we only have installshield 3.1. Is it worth sticking to it? upgrading it? or going .net setup? And why? I've just started searching for articles regarding this but haven't found any concrete answers yet.

If you have any idea, suggestions or comments, it will be greatly appreciated. Thanks!

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Jan Montano19y ago
Thanks a lot for the info. I'm having a hard time justifying installshield. hmmm... Yes, our application is for public release. If anyone knows of an article regarding this, please don't be shy. hehehe. The thing I'm not sure if .net setup is capable of executing sql scripts. is it?
Scott Lysle19y ago
The current version of InstallShield is 2008; whether or not you need it is probably largely dependent upon the complexity of your installations. The .NET setup and deployment package is probably adequate for most things but is a pretty barebones installer, particularly if you are releasing software for internal use. If the software is intended for public release, an InstallShield deployment is probably a better choice since it includes features that do things like force the installer to agree to the end user license agreement.