Comments on: WiX v3.5 supports Visual Studio 2010 beta 2 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/ Bob Arnson on setup and servicing with WiX and MSI Sun, 24 Jul 2011 04:35:22 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Bob Arnson http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/comment-page-1/#comment-7642 Bob Arnson Tue, 15 Dec 2009 02:20:14 +0000 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/#comment-7642 HabSoft, Burn is still in active development for v3.5. HabSoft,

Burn is still in active development for v3.5.

]]> By: HabSoft http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/comment-page-1/#comment-7641 HabSoft Mon, 14 Dec 2009 21:59:38 +0000 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/#comment-7641 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. 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.

]]> By: Bob Arnson http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/comment-page-1/#comment-7640 Bob Arnson Fri, 11 Dec 2009 19:51:57 +0000 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/#comment-7640 HabSoft, Finishing ClickThrough was dropped from WiX v3.0 and moved to v4.0. HabSoft,

Finishing ClickThrough was dropped from WiX v3.0 and moved to v4.0.

]]> By: HabSoft http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/comment-page-1/#comment-7639 HabSoft Fri, 11 Dec 2009 14:39:51 +0000 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/#comment-7639 No Visual Studio on box at this time, looking to install SQL Express 2008 along with a FoxPro application. No Visual Studio on box at this time, looking to install SQL Express 2008 along with a FoxPro application.

]]> By: HabSoft http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/comment-page-1/#comment-7638 HabSoft Fri, 11 Dec 2009 14:37:39 +0000 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/#comment-7638 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. 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.

]]> By: Will http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/comment-page-1/#comment-7599 Will Mon, 02 Nov 2009 14:33:48 +0000 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/#comment-7599 Bob, what's the best option that will work both on development and build machines? Bob, what’s the best option that will work both on development and build machines?

]]> By: Bob Arnson http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/comment-page-1/#comment-7598 Bob Arnson Mon, 02 Nov 2009 13:14:54 +0000 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/#comment-7598 Will, Yes, it's still open, so the bug still exists. Have you considered using alternate ways of pointing to your content? http://www.joyofsetup.com/2009/01/01/choosing-your-payloads/ Will,

Yes, it’s still open, so the bug still exists. Have you considered using alternate ways of pointing to your content? http://www.joyofsetup.com/2009/01/01/choosing-your-payloads/

]]> By: Will http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/comment-page-1/#comment-7597 Will Mon, 02 Nov 2009 12:54:49 +0000 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/#comment-7597 Are web application installations still hosed (ID 2886669)? Are web application installations still hosed (ID 2886669)?

]]> By: Christopher Painter http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/comment-page-1/#comment-7596 Christopher Painter Sat, 31 Oct 2009 11:53:29 +0000 http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/#comment-7596 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. 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.

]]>