Microsoft Visual Studio Installer Projects

Microsoft Free

This official Microsoft extension provides support for Visual Studio Installer Projects in Visual Studio 2013

(61) Review
Visual Studio
Download (38,254)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (61)
Q and A (51)
Sign in to write a review
Sort by:

by Tlford | Thu 12:27 AM

Is there anyone out there who could fix this project to be able in install to XP. Now I will have to manually fix my WIX installer. What fun.

by kjbartel | August 12 2014

It's great to have support for building old VS installer projects in VS2013 and it will really help people move away from using VS2010. Unfortunately though it's not that great for anything other than legacy programs. New ClickOnce setup packages for newer components don't seem to be getting released meaning you have to try and roll your own if you update your programs to use any newer components. To make it worse, the old Bootrapper Manifest Generator has disappeared from MS's website so making those packages is just that little bit harder and time consuming.
I can't help but feel that this extension is a half-hearted attempt to appease all the users who wanted proper support for these projects. It's clear that proper support won't be given though. ClickOnce and VS installer projects are pretty much dead in the eyes of MS. I just wish MS would provide a viable alternative other than ISLE or the not very user friendly WiX. We still need to write desktop apps and we need a good easy to configure and build installer. This isn't it.

by ICCSol | August 05 2014

Works brilliantly, but being unable to deploy to XP machines is an absolute dealbreaker.

by pavel.grishanov | August 01 2014

Can not be installed on 2013 Express Edition SP2:
Visual Studio is required but its not installed.
"Don't check for the version,check for a feature" - Blog from one of the MS manager.

by Mariano Beeche | July 25 2014

Before this extension I had to keep older versions of Visual studio just to generate a installer. Great tool, THANKS!

by Roberrt Greengrass | July 24 2014

Don't work on 2013 Express edition.

by D.Hammink | July 21 2014

Great tool I really don't like the Installshield. Just for simple Setup projects this is enough.
Next move add Install for a Service (used to work in 2010 )

Keep on going .

by Scaasic | July 16 2014

No guide available for how to use this extension.

by Nii Okai Addy | July 09 2014

by Jay (CTI Developer) | July 09 2014

May your higher power bless you. Having this extension has saved my bottom-side.

Yes, I have the WinXP problem. I intend to follow Xian's post.

But otherwise, this is way more easier to use than the other MS provided solutions.

Thank you!

by mr_super_genius | July 03 2014

Good to see this back! The one provided with VS 2013 was very limited

by PeterŠulek | July 01 2014

by Marcel Raad | June 28 2014

The installers don't work on Windows XP and Server 2003. Unfortunately this is a blocker for me. Apart from that, this extension is great. Thank you very much for bringing it back!

by daniel.pereira | June 26 2014

The MSIs produced by this extension do not work on Windows 2003 or XP.

by David Lowndes | June 24 2014

Nice to hear that you've fixed the "Error 2727 occurring with more than 1 content file" problem I reported, but my other issue of only being able to load a solution once is still a bug in V1. :(

... but applying update 2 (I was using VS2013 update 1), appears to have resolved the subsequent solution loading issue.

Now, how about having a setup that will work on XP generation OS's?

by Viktar | June 19 2014

Thank you for bringing it back. Finally I can uninstall Visual Studio 2010.

by Fred Iannon | June 16 2014

If anyone figures out a way to get around the problem with the msi running in XP please let me know. I have been worked on this for a while by editing the .msi with Orca and did make progress getting it to work, however it then caused another problem if the installer also had custom actions (the previous 1001 error appeared)

by Edwin_C | June 16 2014

The version still cannot build msi which can be run in Windows XP. Will this be fixed? Or XP was totally abandoned by Microsoft?

by Mike E Yeager | June 15 2014

Good to have you back!

by Peter Wimmer | June 14 2014

It's really good news that the Microsoft Visual Studio Installer Projects are back.

I wish you could fix the issues that already bothered me in VS2010:

1) Desktop icons created by the installer on the desktop are limited to 48x48 pixels and look bad on high-DPI displays. This applies even when the application icon includes higher resolutions, it's an installer issue, not an issue of the icons.

2) Add an option to set DISABLEADVTSHORTCUTS for icons. Otherwise installing updates of the applications breaks shortcuts the user has manually attached to the taskbar.

3) Enable antialiasing in the dialog fonts.

1 - 20 of 61 Items   
Sign in to start a discussion

  • Crash after install Visual Studio 2013 Update 3
    5 Posts | Last post Wed 4:58 PM
    • This extension begins to crash Visual Studio after install Visual Studio 2013 Update 3.
      When I open a solution that contains a install project, Visual Studio crashes with the following exception:
      Application: devenv.exe
      Framework Version: v4.0.30319
      Description: The process was terminated due to an unhandled exception.
      Exception Info: System.NullReferenceException
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__4(System.Object)
         at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
         at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
         at System.Windows.Threading.DispatcherOperation.InvokeImpl()
         at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
         at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
         at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
         at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
         at System.Windows.Threading.DispatcherOperation.Invoke()
         at System.Windows.Threading.Dispatcher.ProcessQueue()
         at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
         at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
         at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
         at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
         at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    • Well, it looks that the problem is Between "WebEssentials for Visual Studio Update 3" and "Installer Project Extensions".
      When uninstall "Visual Studio Installer Projects" everything works fine even with WebEssentials enabled. If reinstall  "Visual Studio Installer Projects" and set to disabled WebEssentials everything works well.
      These two extensions don´t work together.
    • I report this as an issue for WebEssentials 2013
    • Thanks for the workaround. I was experiencing the same issue and disabling Web Essentials 2013 does "fix" the problem.
    • I can confirm this as a problem as well. What I don't understand is why is would web essentials have anything to do with a windows project with setup?  I was flailing around uninstalling extensions trying to open a project I was having an error on a user machine to debug and boom, devenv crashed.  Thanks for working through the problem so we have a workaround.  Is web essentials putting out an update or is this project going to issue an update?
  • Definition of Installer Properties
    1 Posts | Last post Wed 12:42 PM
    • In the Visual Studio 2010 Setup Project it was possible to define Installer Properties (by defining conditions).
      In the Visual Studio 2013 Installer Projects Extension I could not do this.
      Please add this functionality to Visual Studio 2013 Installer Projects Extension or if it is already included let me know how to use it.
      For example I would like to set ARPNOREPAIR=1
  • Installers on 2012 R2
    2 Posts | Last post August 21, 2014
    • I having difficulty with the Web Setup Projects on a server running 2012 R2, I just have the 4.5 Framework enabled and IIS with IIS6 compatibility installed.
      The install fails and in the logs I am seeing this:
      INFO   : [07/31/2014 14:57:51:076] [RegisterAspNet                          ]: Reading registry value Path from key 'HKLM\Software\Microsoft\ASP.NET\1'...
      INFO   : [07/31/2014 14:57:51:076] [RegisterAspNet                          ]: Using 64 bit registry key...
      MSI (s) (C8!04) [14:57:51:076]: Note: 1: 2262 2: Error 3: -2147287038 
      MSI (c) (FC:40) [14:57:51:076]: Note: 1: 2262 2: Error 3: -2147287038 
      DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog
      The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog, 
      Error 1402. Could not open key: Software\Microsoft\ASP.NET\1.  System error 2.  Verify that you have sufficient access to that key, or contact your support personnel.
      MSI (s) (C8!04) [14:57:54:420]: Note: 1: 2262 2: Error 3: -2147287038 
      MSI (s) (C8!04) [14:57:54:420]: Product: TestWebApplicationSetup -- Error 1402. Could not open key: Software\Microsoft\ASP.NET\1.  System error 2.  Verify that you have sufficient access to that key, or contact your support personnel.
      ERROR  : [07/31/2014 14:57:54:420] [RegisterAspNet                          ]: FAILED:	-2147024894
      ERROR  : [07/31/2014 14:57:54:420] [RegisterAspNet                          ]: Custom Action failed with code: '0'
      INFO   : [07/31/2014 14:57:54:420] [RegisterAspNet                          ]: Custom Action completed with return code: '2'
    • I was getting the same error, could you able to resolve this error?
  • Will this be incorporated into VS2014?
    2 Posts | Last post August 18, 2014
    • Please!
      And please make it generate setups that work on XP/Server 2003 OS's - without having to faff around.
    • This SHOULD suppport Visual Studio 2014 (or 14).
  • Can Setup project be build from command line using msbuild ?
    1 Posts | Last post August 07, 2014
    • Does anyone know if Setup project can be build from command line using msbuild ?
  • Extension doesn't work
    2 Posts | Last post August 06, 2014
    • I have downloaded and installed the extension, but the new Project types don't appear in the "New project" window. I've tried it twice (on different machines) and I tried to repair the installation of VS and the extension. I'm using VS 2013 (Update 2) with the German and English language-pack on a 32-bit Windows.
    • I found out that I had a Problem with updating SQL Server Data Tools. Since I re-installed the update, the extension works well.
  • How do I target users documents folder
    1 Posts | Last post July 25, 2014
    • I am trying to create an installer that will include PowerShell modules.  These need to live in a very specific sub directory of the user's my documents folder.  How do I specify this on the Target File System UI?
  • Can't install Extension
    1 Posts | Last post July 24, 2014
    • I have tried several times to download this extension, but it fails every time I attempt the install. I do have VS 2013 installed. Hoping someone can decipher this section of the log file:
      [0978:213C][2014-07-24T10:43:41]i301: Applying execute package: VSI_MSI.msi, action: Install, path: C:\ProgramData\Package Cache\{711C01FD-667A-4F81-8C85-BBE08ADDAD1D}v12.0.30122\packages\VSI\VSI_MSI.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" VSEXTUI="1"'
      [0978:213C][2014-07-24T10:43:41]e000: Error 0x80070643: Failed to install MSI package.
      [0978:213C][2014-07-24T10:43:41]e000: Error 0x80070643: Failed to execute MSI package.
      [12E0:21E8][2014-07-24T10:43:41]e000: Error 0x80070643: Failed to configure per-machine MSI package.
      [12E0:21E8][2014-07-24T10:43:41]i000: MUX:  Installation size in bytes for package: VSI_MSI.msi MaxAppDrive: 0  MaxSysDrive: 8192  AppDrive: 0  SysDrive: 8192
      [0978:213C][2014-07-24T10:43:41]i301: Applying execute package: Preparation, action: Install, path: C:\ProgramData\Package Cache\F80E54B4-3896-3E93-830C-55D1291E0EA2\packages\Preparation.exe, arguments: '"C:\ProgramData\Package Cache\F80E54B4-3896-3E93-830C-55D1291E0EA2\packages\Preparation.exe" /l "C:\Users\Eric\AppData\Local\Temp\dd_VSI_bundle_20140724104330_1_Preparation.log"'
      [0978:213C][2014-07-24T10:43:41]e000: Error 0x80070643: Process returned error: 0x80070643
      [0978:213C][2014-07-24T10:43:41]e000: Error 0x80070643: Failed to execute 
  • Automatically Checkout
    1 Posts | Last post July 24, 2014
    • When changing properties (e.g. version number etc.) in my setup project that is under TFS Version control there is no automatic check out. Can you change this?
  • Workaround for Win XP / Win 2003 problem
    8 Posts | Last post July 23, 2014
    • Hi Space!
      For everyone who needs the setup projects to run on Windows XP or Windows 2003, here are steps for a workaround which worked for me.
      - Create a simple dummy setup in Visual Studio 2010 (you just need a VS 2010 .msi).
      - Install the tool “MsiDB” from Microsoft or look if it is installed on your drive (search for “MsiDB.exe”). For me it was on C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin.
      - Start the tool an select the Visual Studio 2010 .msi. Select an export folder.
      - Select “Binary” in the tool, select “Export” and click “OK”. (Now new files are found in the previous selected export folder.)
      - Close the tool!
      - Create your Visual Studio 2013 setup project.
      - Start “MsiDB” again and now select the VS 2013 .msi. Select an OTHER export folder.
      - Select “Binary” in the tool, select “Export” and click “OK”.
      - Now, this is the magic (!). Copy the file “MSVBDPCADLL.ibd” from the VS 2010 export folder to the VS 2013 export folder and overwrite the existing file.
      - Now select “Import” in the tool a select “Binary.idt” and then hit “OK”. (There is no visual response after clicking OK so make sure you click it.)
      - Close the tool with “Quit”.
      - Now you should see, that the last edit date of the VS 2013 .msi changed. Your setup is now ready for WinXP / Win 2003. 
      I have tested it also on Win 2012 R2. It worked for me every time!
      Hope this helps you to.
      Cheers from beautiful Austria! - Xian
    • Do you have to do this every time you build an MSI file or can you do it just the once?
    • The final solution:
      "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\MsiDb.Exe" -f "D:\Temp\VS2010-MSI-IDT" -i Binary.idt -d "C:\TO\VS2013Setup.msi"
      The folder should contain Binary.idt and the folder Binary. They can be extracted just once from VS2010Setup.msi using the following command:
      "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\MsiDb.Exe" -d "C:\TO\VS2010Setup.msi" -f "D:\Temp\VS2010-MSI-IDT" -e Binary
      Thank you, Xian!
    • VBScript Version (once you have extracted MSVBDPCADLL.ibd from a VS2010 MSI):
      Option Explicit
      Const msiOpenDatabaseModeReadOnly = 0
      Const msiOpenDatabaseModeTransact = 1
      Dim Installer
      Dim View
      Dim Record
      Set installer = Wscript.CreateObject("WindowsInstaller.Installer")
      Set Record = Installer.CreateRecord(1)
      Record.SetStream 1, "C:\Binary\MSVBDPCADLL.ibd"
      Dim databasePath:databasePath = Wscript.Arguments(0)
      Dim database : Set database = installer.OpenDatabase(databasePath, msiOpenDatabaseModeTransact)
      Set View = Database.OpenView("UPDATE `Binary` SET `Binary`.`Data` = ? WHERE `Binary`.`Name`='MSVBDPCADLL'")
      View.Execute Record
      WScript.Echo ".MSI Updated"
    • cscript.exe <vbs file> <msi to modify>
    • Thanks, Ty_Trunk !
    • Xian, I don't have Visual Studio 2010 to create dummy setup, all I have is Visual Studio 2013 only
    • Look at the post by Diego Alexander Hoyos David on April 21, 2014.  It may point to an easier way to fix the build process rather than fix the .msi afterward.
1 - 10 of 51 Items