As many of you know, I’ve been using InstallShield a lot at work. For the most part, I really like it although it’s not without it’s share of issues.
Recently, someone asked me why specifically I use InstallShield as opposed to Visual Studio .NET.
Since I’m creating MSI installs, sure the InstallScript is nice but is there anything that I couldn’t do in VS with VB and VBScript? Not having a great answer to the question, I decided it would only be fair to find out. So having said that, I’m going to be doing some research & experimentation on porting my existing work to VS.NET setup kits (as opposed to just doing IS inside VS).
Actually, I’ll be looking at 3 things…
- IS based installs created from within the IS IDE
- IS based installs created from within VS.NET
- VS.NET based installs (created in VS.NET)