With the release of Visual Studio 2010, Microsoft announced that the Visual Studio Installer project template would no longer ship with Visual Studio and, true to their word, there is no Visual Studio Installer project in Visual Studio 2012.
So, what are you meant to do if you need to create an installer package for your application?
If you are creating a Windows Store app then you don't need an installer, as the new deployment model makes installers obsolete. If you are creating a web application then Microsoft would prefer you either use XCopy deployment or the MSDeploy web deployment technology, which means installers are only required for desktop applications, and even for those there's the Click Once deployment technology to make things easier. Even then, there are a set of desktop applications that require installer packagers and if you are building one of those, Microsoft has partnered with InstallShield and included the InstallShield Limited Edition project type in Visual Studio 2012 that you can use. If you don't want to use InstallShield you can always fall back to using WiX for creating projects.
In this recipe we will use InstallShield LE to create an installer package for a simple application.
The recipe assumes you haven't yet installed InstallShield Limited Edition. If you have, then some of the early steps in this recipe will be different.
Simply start Visual Studio 2012, and you're ready to go.
Create an installer using these steps:
Simple
WPF
Application
.C:Program Files (x86)Microsoft Visual Studio 11.0Common7IDEItemTemplatesCSharpGeneral1033IconIcon.ico
.Simple
WPF
Application
.Setup1
project in Solution Explorer and select Install from the menu. If prompted to build out of date projects, click on Yes.Setup1
project and selecting Uninstall.InstallShield reduces the complexity in creating installers by providing a set of sensible default configuration options and an easy to use user interface. It also understands exactly how the Windows installer system works and warns when there are problems in how you have configured the installation process. For example, if you look at the warning outputs from the recipe when the package was built, you would have seen a warning about the .NET Framework and how it would be a good idea if that was included with the setup kit to ensure people who don't have .NET already installed won't have extra setup dependencies.
While you can achieve the same result using WiX, the amount of work required to get the XML written and debugged to achieve the same result would have made this a much, much longer recipe!
A license for the Limited Edition is provided free of charge with Visual Studio 2012 and will be sufficient for the basic installation purposes. If you need a heavily customized installation process then you should investigate the more advanced versions of InstallShield or competing offerings such as Nullsoft's NSIS.
3.147.47.144