InstallAware 8 is the first and only installation toolkit to support Microsoft's newest technologies released with Visual Studio 2008 Service Pack 1 - Microsoft SQL Server Express 2008, .NET Framework 3.5 with Service Pack 1, and Visual Studio 2008 MFC Runtime with Service Pack 1. We're making this support available in just two weeks after Microsoft released Visual Studio 2008 Service Pack 1 to manufacturing, preserving our tradition of always being[sic] all other vendors to it, including InstallShield!
I found InstallAware's statement very interesting because I've just finished a sprint where I delivered 10 installs in 2 weeks. Each of these installs are components of an SOA based system heavily relying on .NET 3.5 SP1 and SQL Server 2008. It's a brand new product line for our company written by a team that's dedicated to being on the cutting edge of Microsoft technologies.
But how could I have possibly done this work if InstallAware is just now the first vendor ( including InstallShield!! ) to support these technologies?
Easily, I used InstallShield.
As I previously posted, InstallShield has a flexible feature called Prerequisites that allow you to define how to detect and install a component via setup.exe. This is similar to what the WiX team is trying to achieve with burn only InstallShield has had it for years. ( As an aside, burn looks promising, but since it was dropped from WiX release 3.0 due to rosario ship considerations don't expect it to be released for quite a long time to come. ) Using the prerequisite editor, it's a simple 5 minute job to include .NET 3.5 SP1 and the latest MFC runtime ( which we don't use thankfully ) in your install.
Additionally InstallShield's SQL scripts pattern continues to work very well with SQL Server 2008. True, there isn't a dedicated setting that says "Support SQL 2008" but there is a customize checkbox that is far more powerful:
As I've previously posted, don't believe everything you read on the internet.