WiX v3.5 supports Visual Studio 2010 beta 2

So that the WiX Working Group can enjoy Hallowe’en on Saturday, WiX v3.5.1030.0 with support for Visual Studio 2010 beta 2 was released today. You can get the bits at http://wix.sourceforge.net/releases/3.5.1030.0/. This isn’t a full beta release – Burn is still in active development and isn’t ready for prime-time use yet – but we want to support everyone using the beta 2 release of Visual Studio 2010, which shipped last week.

Candy, Visual Studio program manager and WiX Working Group babysitter/cat-herder, had this to say about the features in this release:

Visual Studio 2010 Beta shipped on 10/21. With the team’s hard work and agility, we were able to release the WiX support on VS2010 Beta 2 today! Here are some highlights for this release:

  • Extension Manager Integration – Now you can download and install WiX directly from within the VS IDE by launching Extension Manager
  • Major performance improvement during project building – No more IDE freezing during build
  • Automatic upgrade from VS2008 to VS2010 – no more manual editing of wixproj files to change the tools version
  • Improved IDE experience including drag/drop of nodes, copy/paste of items, and project references
  • Added Visual Studio 2010 Express products detection in the WiX VS Extension – New in Beta
  • Over 40 + bug fixes

I’m pleased we were able to get a release supporting beta 2 out so quickly and I’m very excited about the “no more IDE freezing during build” improvement. There are several other smaller enhancements that will make WiX v3.5 a no-brainer upgrade when it ships next year.

In the meantime, if you’re using Visual Studio 2010, please grab this build and be on the lookout for future weekly releases. Problems, questions? Send mail to wix-users, file bug reports, or submit feature requests.

9 thoughts on “WiX v3.5 supports Visual Studio 2010 beta 2”

  1. Congratulations on the performance fix. I’ve seen it around for a couple of years and I’ve also spent some time learning how to do VS SDK work and it’s not easy stuff.

    Now if InstallShield would just fix their stuff. :-) Their VS integration is so bad that we have to use a script to add and remove projects from the solution to use msbuild at build time. We don’t even attempt to open the solution up in our dev environment. I guess InstallShield never thought that you would have dozens of projects in one solution.

  2. ClickThrough blew up on recently formatted Windows 7 64 bit box:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ArgumentException: Win32 handle that was passed to Icon is not valid or is the wrong type.
    at System.Drawing.Icon..ctor(IntPtr handle, Boolean takeOwnership)
    at System.Drawing.Icon..ctor(IntPtr handle)
    at System.Drawing.Icon.FromHandle(IntPtr handle)
    at Microsoft.Tools.WindowsInstallerXml.Extensions.ClickThrough.NativeMethods.GetDirectoryIcon(Boolean small, Boolean open)
    at Microsoft.Tools.WindowsInstallerXml.Extensions.ClickThrough.PickEntryStep..ctor()
    at Microsoft.Tools.WindowsInstallerXml.Extensions.IsolatedAppClickThroughUI.GetControls()
    at Microsoft.Tools.WindowsInstallerXml.Tools.ClickThrough.WorkPage.InitializeFromFabricator()
    at Microsoft.Tools.WindowsInstallerXml.Tools.ClickThrough.WorkPage.set_Extension(ClickThroughUIExtension value)
    at Microsoft.Tools.WindowsInstallerXml.Tools.ClickThrough.ClickThroughForm.ShowWorkPage(Object sender, ClickThroughUIExtension extension)
    at Microsoft.Tools.WindowsInstallerXml.Tools.ClickThrough.WelcomePage.ComboBox_SelectedIndexChanged(Object sender, EventArgs e)
    at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
    at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
    at System.Windows.Forms.ComboBox.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    —————————————-
    ctui
    Assembly Version: 3.0.0.0
    Win32 Version: 3.5.1030.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Windows%20Installer%20XML%20v3.5/bin/ctui.exe
    —————————————-
    System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    —————————————-
    System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    —————————————-
    System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    —————————————-
    wui
    Assembly Version: 3.0.0.0
    Win32 Version: 3.5.1030.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Windows%20Installer%20XML%20v3.5/bin/wui.DLL
    —————————————-
    wix
    Assembly Version: 3.0.0.0
    Win32 Version: 3.5.1030.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Windows%20Installer%20XML%20v3.5/bin/wix.DLL
    —————————————-
    System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    —————————————-
    System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    —————————————-
    WixIsolatedAppExtension
    Assembly Version: 3.0.0.0
    Win32 Version: 3.5.1030.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Windows%20Installer%20XML%20v3.5/bin/WixIsolatedAppExtension.DLL
    —————————————-
    wconsole
    Assembly Version: 3.0.0.0
    Win32 Version: 3.5.1030.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Windows%20Installer%20XML%20v3.5/bin/wconsole.DLL
    —————————————-
    WixOfficeExtension
    Assembly Version: 3.0.0.0
    Win32 Version: 3.5.1030.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Windows%20Installer%20XML%20v3.5/bin/WixOfficeExtension.DLL
    —————————————-

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

  3. OK thanks. It did seem too good to be true. I’d settle for a WIX 3.5 code fragment to install SQL Express 2008. Most of the SQL Server world is watching for the WIX 3.5 carrot out of the corner of their eye, because installers are really a nightmare.

Comments are closed.