[UPDATE 04/18/14] The Visual Studio team has released an extension to VS 2013 to address the feedback on this, which has been loud and clear for a long time now:. [UPDATE 11/6/12] Fixed broken links. At the user group meeting last night, someone asked about the future of. There was some confusion over the future of WiX since at one point there to ship it but then that., who leads the WiX project, is a developer on Visual Studio, and Visual Studio continues to contribute to the WiX project. We use WiX to create the installation packages for VS and a bunch of other stuff.

The Visual Studio setup projects will not ship again – VS 2010 was the last release with support for it. So, you’ll want to make plans to migrate to something else. Of course, I’d suggest looking into WiX, and there are other options as well. The MSDN page contains a table showing a comparison of VS setup projects, WiX, and InstallShield Limited Edition.

This article will show you how to use InstallShield LE From VS2012 to. Simple Steps to Create Setup File Using. If you want to download the Express Edition then. We recommend that you use InstallShield Limited Edition for Visual Studio. If you convert the project to. SQL Server Compact Edition: Visual Studio 2013 doesn't.

Caution Future versions of Visual Studio will not include the Visual Studio Installer project templates. To preserve existing customer investments in Visual Studio Installer projects, Microsoft will continue to support the Visual Studio Installer projects that shipped with Visual Studio 2010 per the product life-cycle strategy. For more information, see. Hi Buck, As you recommend we use InstallShield 2011 LE for our Visual Studio 2010 setups. It has now turned out, that InstallShield has problems with an automatic build (MSBuild.exe). When the account which builds the solutions has NO administrative priviledges, the build fails every time with the message: 'C:Program FilesMSBuildInstallShield2011LimitedInstallShield.targets(96,3): error: -7159: The product license has expired or has not yet been initialized.' InstallShield Support was not very helpful in this case.

So the problem still exists and is very anoying. So if InstallShield doesn't fix this problem, we don't recommend InstallShield LE Perhaps Microsoft can have an eye on that? My issue with WIX is that COM registration in WIX seems to be very difficult. I was excited about going to it until after reading numerous forums the best way to use it was to keep track of each individual COM registration that goes into the registry in your WIX script. Our application is based a lot on ESRI ArcGIS libraries that are all written in COM and require COM registration for almost everything we do. To keep up with these COM entries in WIX (one by one) just isn't going to bode well with our developers. It was frustrating when I tried to use it for this.

If our project didn't have COM, it looks like it would be a great installer package to use. This decision to remove support for setup projects is very, very wrong. We installed Visual Studio 2012 and were just SHOCKED and very irritated! We have Windows Services that are part of our offering that need to be installed. As noted InstallShield LE is very weak and does not support this. Feeding Frenzy 4 Free Download Full Version For Pc.

Forcing us towards an expensive and paid option on InstallShield is really appropriate. That we cannot put together a simple deployment to get a project that we build in VS 2012 is just downright stupidity on behalf of the Visual Studio team.