Microsoft Visual Studio Installer Projects

Microsoft Free

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

Microsoft
(57) Review
Visual Studio
2013
Download (29,007)
6/15/2014
1.0.0.0
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (57)
Q and A (45)
Sign in to write a review
Sort by:

by Mariano Beeche | Fri 4:05 PM

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

by Roberrt Greengrass | Thu 7:49 AM

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 1.0.0.0 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.

by Sriram Kalyanasundaram | June 10 2014

I don't understand why this is included in VS 2013 by default. I don't want to install any third party components for the components I built through VS 2013.The edition that is provided for free doesn't allow you to do lot of stuff since it is a limited edition. I would like to have the Setup and Deployments project back to do this! This was so easy in older versions of Visual Studio. I hope installing this extension solves my issue.

by Adam Floyd | June 09 2014

Nowhere is it made clear that this does not work with the Visual Studio Express edition. Trying to install it with VS Express misleadingly informs me that Visual Studio is not installed. Please clarify the exact products it supports in the above information, and mention that Express editions are not supported in the error message - its current form is very misleading as it suggests there are no VS products installed at all.

by NinaMariaP | June 05 2014

Very cool. Thank you

by Daniel Castenholz | June 01 2014

Finally!!

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


  • How do I target users documents folder
    1 Posts | Last post Fri 12:28 AM
    • 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?
      
      Thx,
      Adam
  • Can't install Extension
    1 Posts | Last post Thu 2:45 PM
    • 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 Thu 7:26 AM
    • 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 Wed 10:06 PM
    • 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
      Database.Commit
      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.
  • Error 2835
    9 Posts | Last post Wed 10:02 PM
    • When build a project that works fine in Visual Studio 2010 and invoke custom actions occurs an error:
      
      DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog
      El instalador encontró un error inesperado al instalar este paquete. Esto puede indicar un problema con este paquete. El código de error es 2835. Los argumentos son: ErrorIcon, ErrorDialog, 
      Error 1001. Error 1001. InstallUtilLib.dll: Unknown error.
      MSI (s) (8C!08) [13:17:12:426]: 
      DEBUG: Error 2769:  Custom Action _E8C2335F_8251_4C1A_8B0C_AEF0D1161778.install did not close 1 MSIHANDLEs.
      El instalador encontró un error inesperado al instalar este paquete. Esto puede indicar un problema con este paquete. El código de error es 2769. Los argumentos son: _E8C2335F_8251_4C1A_8B0C_AEF0D1161778.install, 1, 
      CustomAction _E8C2335F_8251_4C1A_8B0C_AEF0D1161778.install returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
      La acción terminó a las 13:17:12: InstallExecute. Valor devuelto 3.
      Acción 13:17:12: Rollback. Revertir la acción:
    • After compare the msi generated in VS 2010 and 2013 I found two differences:
      1.) In the binary table: MSVBDPCADLL file 
      2.) In the file table: dll that contains custom action has wrong file size
      
      After many test the only way that the setup works correctly is when replace the file "MSVBDPCADLL" in the msi with a VS2010 version. It also works when replace the file dpca.dll from directory "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\Deployment" to directory "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\VSI\bin"
      
      For this test create a basic setup project that invokes a custom action dll that contains installer class. I work in Windows 8.1 Update x64 with Visual Studio 2013 Premium.
    • Thanks Diego for the work on reporting this - We're looking into it.
      
      Tony Goodhew, Program Manager, VS Pro.
    • Amazing Diego! I was in need of a fast solution and the workaround to replace the old dll saved my day, Thanks!
    • Very thanks.
    • Great Diego, many thanks!
      Rolf
    • Hi,
       I have replaced the dpca.dll from directory "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\Deployment" to directory "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\VSI\bin" , but still i get the same error Error 1001. InstallUtilLib.dll: Unknown error.
      
    • Hi Diego,
      
       When i replace the dll, as suggested, then if i click on the setup project and click on install , then there is message saying that you need .Net 4.5 to run this setup. But when i dont replace the dll it shows the message Error 1001. InstallUtilLib.dll . Can you please let me know how to resolve this
    • I believe that once you replace the file, you need to rebuild the setup project.
  • setup blocked
    3 Posts | Last post Wed 7:52 PM
    • I downloaded "Microsoft Visual Studio Installer Projects" on my computer. And when I try to install it I face "Setup Blocked" message.
      And the reason describes in this way:
      
      "Microsoft Visual Studio is required, but it is not installed on this computer. Please install it and retry."
      
      While I've already have "VS Express 2013 for Desktop". What is the solution?
      
    • We have the same problem.
      Sorry I'm not helpful.
    • I don't believe that extensions may be used with VS Express.
  • Does this work on Windows Server 2003 with .NET Framework 4.0 ?
    1 Posts | Last post July 21, 2014
    • Does this work on Windows Server 2003  with .NET Framework 4.0. I don't have Visual Studio 2010 to create Dummy setup ?
  • Cannot install this template
    1 Posts | Last post July 16, 2014
    • I want to install this template on my computer and my Visual Studio 2013 Express but the install report me that no Visual Studio in my computer.
      I opened the Log File and the install search for Professional edition.
      Do I must to have Professional Edition?
      Or it's all about the install not found my Visual Studio files in Hard Disk (C:) cause the files in (D:) Hard Disk?
  • Not able to build .vdproj in TFS
    1 Posts | Last post July 16, 2014
    • Hi, I am not able to build .vdproj in TFS, does anyone have a solution for this ?
  • Installs don't work on XP
    9 Posts | Last post July 03, 2014
    • Just discovered that all of my installers fail when used on an XP system - this is worrying, because our customer site has a number of XP boxes and I will need to deploy applications to these.
      
      For information, my XP test systems are on Virtual PCs. Installers created in VS2010 still work fine. I have tried upgrading the Windows Installer version  on the XP machines from 3.1 to 4.5, but this makes no difference.
      
      The new installers work fine on Windows 7 and 8.1, but I need them to work on XP.
    • This is also an issue for my. It fails with an 1603 in the event log.
    • I wonder if this is caused by the problem with custom installer actions? It seems to fail in the built-in custom action DIRCA_CheckFX, which is checking that the specified .NET framework is installed. It happens after id did the install of the .NET 4.0 framework. An excerpt of the installation log looks like this:
       
      Action 20:32:53: DIRCA_CheckFX. 
      Action start 20:32:53: DIRCA_CheckFX.
      MSI (c) (A8:00) [20:32:53:632]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'DIRCA_CheckFX' 
      MSI (c) (A8:00) [20:32:53:632]: Creating MSIHANDLE (1) of type 790542 for thread 3328
      MSI (c) (A8:18) [20:32:53:632]: Invoking remote custom action. DLL: C:\DOCUME~1\XPMUser\LOKALE~1\Temp\MSI364.tmp, Entrypoint: CheckFX
      MSI (c) (A8:84) [20:32:53:632]: Cloaking enabled.
      MSI (c) (A8:84) [20:32:53:632]: Attempting to enable all disabled privileges before calling Install on Server
      MSI (c) (A8:84) [20:32:53:632]: Connected to service for CA interface.
      MSI (c) (A8:18) [20:32:53:992]: Closing MSIHANDLE (1) of type 790542 for thread 3328
      Action ended 20:32:53: DIRCA_CheckFX. Return value 3.
      
      So maybe fixing the custom installer problem will also make this work?
    • Any plans as to when the "Microsoft Visual Studio Installer Projects Preview" will support installs for Windows XP? Or if it will never support Windows XP, since XP is no longer supported?
      
      Is there known solution around this issue for installing to Windows XP? Could the DIRCA_CheckFx be ignored or skipped?
    • Version 1.0.0.0 still fails to generate msi which can run in XP.  Very disappointing!
    • 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)
      
    • 不支持XP,令人失望。失望、失望、失望!
    • 强烈要求,增加对XP的支持。
    • You can use my workaround. See my post on 03.07.2014.
1 - 10 of 45 Items