Re: [WiX-users] Burn, MsiPackage and DisplayInternalUI
Hi Peter, I was created the feature request on 10th July, but no progress still. Could you please follow up this feature, since we have close to release. Thanks, Kannan -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-MsiPackage-and-DisplayInternalUI-tp7484106p7582587.html Sent from the wix-users mailing list archive at Nabble.com. -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn, MsiPackage and DisplayInternalUI
Wix is open source. If you need a feature urgently, you're welcome to take the source code and implement a solution yourself :) Otherwise it's a case of hoping someone on the WiX team (or some other contributor) takes it on. -Original Message- From: Kannan24 [mailto:skan...@syncfusion.com] Sent: 31 December 2012 08:46 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Burn, MsiPackage and DisplayInternalUI Hi Peter, I was created the feature request on 10th July, but no progress still. Could you please follow up this feature, since we have close to release. Thanks, Kannan -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-MsiPackage -and-DisplayInternalUI-tp7484106p7582587.html Sent from the wix-users mailing list archive at Nabble.com. - - Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Transition from InstallShield to WiX
FWIW, you might want to leave open the possibility of InstallShield *AND* WiX. I find that the two compliment each other nicely in agile / democratization scenarios. I'm always available for a telephone chat for anyone who'd like to know what I mean by this. From: Rob Mensching r...@robmensching.com Sent: Friday, December 28, 2012 10:46 PM To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Transition from InstallShield to WiX Easiest way is to use dark to decompile your MSI. Burn (the WiX toolset bootstrapper) creates Bundles that can install prerequisites and far more. For example, the Visual Studio install (~130 packages) uses Burn to install. On Fri, Dec 28, 2012 at 2:40 PM, Richard J Otter r...@columbia.edu wrote: Can anyone point me to a web resource that would ease the transition from InstallShield to WiX? I've been using DTF for several years writing custom actions for InstallShield. I'm interesting in giving the rest of WiX a try. I'm specifically confused about the Wix bootstrapper and how it is involved with the msi GUI. (huh?) I assumes a bootstrapper for WiX would be like the bootstrapper for IS in that it could install prerequisites. Thanks. Richard -- Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching http://RobMensching.com LLC -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.7 Woes with VS2008
3.5 SP1 is installed. I turned on the fusion log and found the entry below. Not quite sure what to make of it. Running the candle.exe command-line that VS2008 produces directly works with entries indicating v4.0.30319 is being used. So this *feels* like, VS2008 is using CLR2 and candle.exe wants CLR4 and somehow the way VS2008 launches candle.exe keeps CLR2 in play? I'm reaching... *** Assembly Binder Log Entry (12/31/2012 @ 9:12:23 AM) *** The operation failed. Bind result: hr = 0x8013101b. No description available. Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll Running under executable C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe --- A detailed error log follows. === Pre-bind state information === LOG: User = snip LOG: Where-ref bind. Location = C:\Program Files\WiX Toolset v3.7\bin\candle.exe LOG: Appbase = file:///C:/Program Files/Microsoft Visual Studio 9.0/Common7/IDE/ LOG: Initial PrivatePath = NULL LOG: Dynamic Base = NULL LOG: Cache Base = NULL LOG: AppName = NULL Calling assembly : (Unknown). === LOG: This bind starts in LoadFrom load context. WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load(). LOG: Using application configuration file: C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.Config LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config. LOG: Attempting download of new URL file:///C:/Program Files/WiX Toolset v3.7/bin/candle.exe. LOG: Assembly download was successful. Attempting setup of file: C:\Program Files\WiX Toolset v3.7\bin\candle.exe LOG: Entering run-from-source setup phase. ERR: Error extracting manifest import from file (hr = 0x8013101b). ERR: Failed to complete setup of assembly (hr = 0x8013101b). Probing terminated. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, December 28, 2012 5:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 3.7 Woes with VS2008 Is the NETFX 3.5 installed on that machine? If so, can you try running with fusion logging turned on? That should pinpoint the assembly causing the problem. On Fri, Dec 28, 2012 at 12:44 PM, Maillet, Ed email...@unum.com wrote: A bit more details. Wix 3.6.3303.1 works just fine on the same project. Something got broke with Wix3.7. Haven't quite figured out what yet. The Wix 3.7.1224.0 build is the one that fails. The RC 3.7.1119.0 fails differently: The ReadRegistry task could not be loaded from the assembly C:\Program Files\MSBuild\..\WiX Toolset v3.7\bin\WixTasks.dll. Could not load file or assembly 'file:///C:\Program Files\WiX Toolset v3.7\bin\WixTasks.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. Confirm that the UsingTask declaration is correct, and that the assembly and all its dependencies are available. C:\Program Files\MSBuild\Microsoft\WiX\v3.x\wix200x.targets I did get error message on another machine with Wix 3.7.1224.0 installed from VS2008: Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: devenv.exe Problem Signature 02: 9.0.30729.1 Problem Signature 03: 488f2b50 Problem Signature 04: mscorlib Problem Signature 05: 2.0.0.0 Problem Signature 06: 503f022f Problem Signature 07: 1c8b Problem Signature 08: b Problem Signature 09: System.BadImageFormatException OS Version: 6.1.7600.2.0.0.256.4 Locale ID:1033 Additional information about the problem: LCID: 1033 - Ed -Original Message- From: Maillet, Ed Sent: Friday, December 28, 2012 11:09 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix 3.7 Woes with VS2008 Hey all, I'm trying to build an existing wixproj in VS2008 that was created using Wix3.5. When I build in Visual Studio, Visual Studio simple dies (ie. The process gets removed from the process list and the UI disappears from the screen). When I build using devenv from the command-line, I do get an error message: Could not load file or assembly 'file:///C:\Program Files\WiX Toolset v3.7\bin\candle.exe' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. I made of copy of the code base and upgraded it to VS2012. Building in VS2012 works just fine. Unfortunately, doing that upgrade for real isn't an option in the actual code base. I have .NET 4.5 installed on the machine and it's Windows 7 SP1. - Ed -- Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft
Re: [WiX-users] No progress in msi progressbar when packed in burn
Hi Jim, It is a bug in 3.6 that I logged. I am not sure if it will be fixed in 3.7 Cheers and Happy New Year, Steve -Original Message- From: J Rao [mailto:jr...@live.com] Sent: December-26-12 2:59 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] No progress in msi progressbar when packed in burn Hi, I have a msi installer built in WiX 3.6, this installer needs .NET framework to be installed first, so I created a bootstrapper project for it using burn. I did have to some heavy modification to make the installerand bootstrapper fit visually but it is finally working, exceptone thing: During install of msi, the progressbar in it doesn't have any progress, the ActionText is still working, but the progressbar is stuck at 0%. This does not happen if I install the msi outside the bootstrapper exe (although in this case the progressbar doesincrease, it goes to 100% very quickly and then start from 0 again, not sure if this is normal or not). I did have to change the msi a lot, including creating my own welcome dialog, and use WixExitEarlyWithSuccess to skip the exit dialog. I checked the log using /l*v but didn't find anything suspicious. Any ideas on what I should try next? Thanks Jim -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.7 Woes with VS2008
No, you've hit it. The straight forward workaround is to add RunWixToolsOutOfProctrue/RunWixToolsOutOfProc to your project file. Fixing the root issue is something I'll do first thing in the WiX v3.8 branch. Unfortunately, that work around will be necessary when using WiX v3.7 in VS2008. On Mon, Dec 31, 2012 at 6:52 AM, Maillet, Ed email...@unum.com wrote: 3.5 SP1 is installed. I turned on the fusion log and found the entry below. Not quite sure what to make of it. Running the candle.exe command-line that VS2008 produces directly works with entries indicating v4.0.30319 is being used. So this *feels* like, VS2008 is using CLR2 and candle.exe wants CLR4 and somehow the way VS2008 launches candle.exe keeps CLR2 in play? I'm reaching... *** Assembly Binder Log Entry (12/31/2012 @ 9:12:23 AM) *** The operation failed. Bind result: hr = 0x8013101b. No description available. Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll Running under executable C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe --- A detailed error log follows. === Pre-bind state information === LOG: User = snip LOG: Where-ref bind. Location = C:\Program Files\WiX Toolset v3.7\bin\candle.exe LOG: Appbase = file:///C:/Program Files/Microsoft Visual Studio 9.0/Common7/IDE/ LOG: Initial PrivatePath = NULL LOG: Dynamic Base = NULL LOG: Cache Base = NULL LOG: AppName = NULL Calling assembly : (Unknown). === LOG: This bind starts in LoadFrom load context. WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load(). LOG: Using application configuration file: C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.Config LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config. LOG: Attempting download of new URL file:///C:/Program Files/WiX Toolset v3.7/bin/candle.exe. LOG: Assembly download was successful. Attempting setup of file: C:\Program Files\WiX Toolset v3.7\bin\candle.exe LOG: Entering run-from-source setup phase. ERR: Error extracting manifest import from file (hr = 0x8013101b). ERR: Failed to complete setup of assembly (hr = 0x8013101b). Probing terminated. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, December 28, 2012 5:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 3.7 Woes with VS2008 Is the NETFX 3.5 installed on that machine? If so, can you try running with fusion logging turned on? That should pinpoint the assembly causing the problem. On Fri, Dec 28, 2012 at 12:44 PM, Maillet, Ed email...@unum.com wrote: A bit more details. Wix 3.6.3303.1 works just fine on the same project. Something got broke with Wix3.7. Haven't quite figured out what yet. The Wix 3.7.1224.0 build is the one that fails. The RC 3.7.1119.0 fails differently: The ReadRegistry task could not be loaded from the assembly C:\Program Files\MSBuild\..\WiX Toolset v3.7\bin\WixTasks.dll. Could not load file or assembly 'file:///C:\Program Files\WiX Toolset v3.7\bin\WixTasks.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. Confirm that the UsingTask declaration is correct, and that the assembly and all its dependencies are available. C:\Program Files\MSBuild\Microsoft\WiX\v3.x\wix200x.targets I did get error message on another machine with Wix 3.7.1224.0 installed from VS2008: Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: devenv.exe Problem Signature 02: 9.0.30729.1 Problem Signature 03: 488f2b50 Problem Signature 04: mscorlib Problem Signature 05: 2.0.0.0 Problem Signature 06: 503f022f Problem Signature 07: 1c8b Problem Signature 08: b Problem Signature 09: System.BadImageFormatException OS Version: 6.1.7600.2.0.0.256.4 Locale ID:1033 Additional information about the problem: LCID: 1033 - Ed -Original Message- From: Maillet, Ed Sent: Friday, December 28, 2012 11:09 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix 3.7 Woes with VS2008 Hey all, I'm trying to build an existing wixproj in VS2008 that was created using Wix3.5. When I build in Visual Studio, Visual Studio simple dies (ie. The process gets removed from the process list and the UI disappears from the screen). When I build using devenv from the command-line, I do get an error message: Could not load file or assembly 'file:///C:\Program Files\WiX Toolset v3.7\bin\candle.exe' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. I made of copy of the code base and upgraded it to VS2012.
