Bring back the basic setup and deployment project type Visual Studio Installer.
You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it's too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future.
We have just released an extension which delivers the Visual Studio Installer projects functionality present in Visual Studio 2010 for Visual Studio 2013.
To find out more please read Visual Studio Installer Projects Extension
Tony Goodhew, Program Manager, VS Pro
We have more information on the next version of InstallShield Limited Edition that will be included in Visual Studio 2013.
We’d like to thank you all for your comments on this UserVoice entry. We have been discussing the comments on InstallShield Limited Edition (ISLE) raised here with Flexera and we are currently working with them to address the top issues. At this stage we have no plans to include the former Visual Studio Setup Projects in future product versions but we will continue to work with Flexera and the community to ensure Visual Studio customers’ setup needs will be met with no-cost tooling that supports a broad range of scenarios.
Tony Goodhew, Program Manager, VS Pro.
What about those of us stuck with VS2012?!!! We just moved to VS2012 from VS2008! It'll be another five years before they move us again! This sucks!
Unfortunately, it is not clear to me. I recently upgraded from the Visual Studio 2005 version to Visual Studio Express 2013. All I would like is an easy way to make an .msi so that I can install the software on other computers. It would be great to have a manual about this. So far I did not find it.... If someone can help, please let me know
Nezar Alazzabi commented
Where's the start-up button -_-
Probably this was the same guy that developed Windows 8... and forgot the start-up button. :)
Please brink it back!
Why the Visual Studio Installer Projects Extension only for VS2013 ?
How about VS2012...? How about VS2012...?
How about VS2012...? How about VS2012...?
Or Microsoft give up VS2012 !!
At last, InstallShield LE really really sucks....
Is this possible to have extension for VS 2012 ? It is really frustrating that we are supporting for VS 10, VS 13 and skipping VS 12.
Is there any specific reason to skip VS 12 ?
Jerry Jonkers commented
All I wanted to have the simple Setup for a Windows service, I've created. The InstallShield Limited Edition will not work when I install the service on our server. I see a youtube video on how to do this for a Windows Service and they show you with the original Installer. Can I use the Install Shield LE to work for a Windows Service ?
Right Nguyen commented
How to set permissions for files in Visual Studio Installer 2013
Nimish Bhonsale commented
The Visual Studio extension does not seem to work with Custom Installer actions.
I keep getting this error: Error 1001. InstallUtilLib.dll: Unknown error.
Just removing the custom installer makes the Installer work fine.
Jamie Temple commented
This is fantastic news!
One small "niggle"...
If we build our solutions with VS2010, then we will usually encounter 1 'pop-up' message during build, for each setup project, stating:
The command you are attempting cannot be completed because the file 'myProjectSetup.vdproj' is under source code control and is not checked out.
This is totally as expected, as (I think) VS is attempting to update the build version.
The "niggle" is when you try to build the same project in VS 2013 - rather than this "pop-up" message occuring once, it seems to pop-up for every file within the setup ptoject - this can be rather annoying if you are building a website setup project with several 100s of pages.
Holding down the "Enter" key to "ok" each of the pop-up messages works fine, and after a while, my solutions build fine ... it's just a bit annoying ...
... other than that, you guys rock! thanks again!
This is a great news for my team which was stuck in VS2010 just because of this!
Dave Kerr commented
Thanks for this Tony - great news for the community!
Paul Bunn commented
How about adding support for VS2012? My projects make heavy use of SQLCE which is not supported in 2013...
Daniel Ladd commented
Thanks for skipping a version so now I have to upgrade again. If it is just a plugin why not make it for 2012 as well???
Also, why does Microsoft care so much about InstallShield? Microsoft should just worry about their own products and not worry about forcing their customers to pay out the a** to maintain their workflow. If people really need InstallShield they will buy it, the rest of us who don't need it shouldn't be forced to buy it as well, visual studio is expensive enough as is.
Stefan Cuypers commented
Thanks for bringing it back. I will be looking at upgrading to VS2013 now.
We use a lot of merge files (.msm) so ISLE is not an option for us. The new version also does not seem to support them.
Thank you very much.
While this is very welcome news I find it incredible that MS could have been so out of touch about customer needs.