by Mike.Sheen » Mon Mar 23, 2015 4:11 pm
The tale of package and deployment options in Visual Studio is quite a sordid one. I'd love to know the reasons behind the seemingly brain-dead and indecisive direction VS has had in relation to setup and deployment packages.
For quite a while we were at the mercy of the bundled/embedded installshield "lite or whatever they called it back in the day" to create setup and deployment packages in Visual Studio - Which was fine until you needed to something more advanced - like install a service or chain to another MSI or include a merge module - then you had to move to the paid versions of Installshield. From memory we once paid $3,500 or so for the edition of Installshield we needed.
Then VS2010 (or was it 2008?) finally introduced a new standard VS project type for setup and deployment - and it was pretty good, too.
Then they must have remembered whatever backroom deal they'd made with InstallShield, because in VS2012 it was gone and we were back to having "Installshield Limited Edition" being bundled with VS and the default and only project type for setup and deployment. Again - this is an ok solution until you need to do something a bit more advanced, then it's off to the paid upgrades to get your installer working.
Mike Sheen
Chief Software Engineer
Jiwa Financials
If I do answer your question to your satisfaction, please mark it as the post solving the topic so others with the same issue can readily identify the solution