[WiX-users] Help with VB DLLs and OCXs

2012-07-29 Thread Aaron Gunstone
Hi folks, first time poster (and WIX user) here. Due to customer request, I'm having to convert our InnoSetup based installer to WIX. It's a VB6/DirectX7 app. I believe I have it correctly installing the application, and the core VB dependencies via MS merge modules (oleaut32, msvbvm60, comcat,

Re: [WiX-users] Problems with build on a specific development PC

2012-07-29 Thread Rob Mensching
Try changing your -l burn to -l burn.log. Looks like the engine doesn't like it when you give it a log file with no extension. If that fixes the problem, feel free to file a bug. On Fri, Jul 27, 2012 at 1:48 AM, Bariz Ralph AVL/GRZ ralph.ba...@avl.comwrote: Hi, The second time I recognize a

Re: [WiX-users] Error 0x80004005: Failed to extract all files from container in burn boostrapper

2012-07-29 Thread Rob Mensching
Did you follow the instructions for signing a bundle in the WiX.chm? It's not as simple as signing the final executable. Unfortunately, the error message in the log doesn't point that out. Feel free to open a bug if the signing issue really is the issue. On Fri, Jul 27, 2012 at 7:41 AM, Barry Wark

Re: [WiX-users] Help with VB DLLs and OCXs

2012-07-29 Thread Rob Mensching
Those are operating system files right? Shouldn't you be using a Merge Module to install stuff that isn't your own? On Sun, Jul 29, 2012 at 9:53 AM, Aaron Gunstone aa...@emeraldcitysupply.com wrote: Hi folks, first time poster (and WIX user) here. Due to customer request, I'm having to

Re: [WiX-users] Help with VB DLLs and OCXs

2012-07-29 Thread Aaron Gunstone
I would be delighted to! Unfortunately, no merge modules exist for these three items, as far as I can find. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 29 July 2012 19:32 To: General discussion for Windows Installer XML toolset. Subject: Re:

Re: [WiX-users] Help with VB DLLs and OCXs

2012-07-29 Thread Aaron Gunstone
Ahh, I tell a slight lie - I have now found a merge module for richtx32.ocx here: http://www.installsite.org/pages/en/msi/msm.htm However, when I try and merge it, Candle generates this error: warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramFilesFolder' which

[WiX-users] SxS MFC merge module needs to write to System32. Why?

2012-07-29 Thread Chris Dahl
As part of our MSI installer we include the VC100_MFC and VC100_CRT merge modules, and we expect them to be written to a SxS location in %windir%\winsxs\. However, we've troubleshooting an issue at the moment where in the event viewer on Windows it shows that the installer needs access to the

Re: [WiX-users] SxS MFC merge module needs to write to System32. Why?

2012-07-29 Thread Bob Arnson
On 29-Jul-12 22:11, Chris Dahl wrote: As part of our MSI installer we include the VC100_MFC and VC100_CRT merge modules, and we expect them to be written to a SxS location in %windir%\winsxs\. The VC10 runtime switched back to System32; VC9 was the last to use WinSxS. -- sig://boB

Re: [WiX-users] Stdba HyperlinkTheme

2012-07-29 Thread Bob Arnson
On 27-Jul-12 12:38, Neil Sleightholm wrote: That sort of works; if I add the image to the Install page it displays on that page but not on options but it still displays on Help. If I move the image to the Help page it displays on all pages. I have tried setting Visible=no but it still

Re: [WiX-users] MsiProperty on the fly and Minor upgrade/downgrade.

2012-07-29 Thread Bob Arnson
On 27-Jul-12 06:51, Ing. Tomáš Kubík, Tempo IS wrote: But downgrade with install mode is doing nothing. If i try repair mode, the installation failed with this log: The method Burn uses to repair apparently won't downgrade. I don't see a workaround so feel free to file a feature request. --