Re: [WiX-users] Detect Windows installer version...
Hello, Thanks a lot for your answer. But... hmmm... I'm not sure my message clearly described my problem. The installed software runs on both WinXP SP1 and SP2 (provided the VC8 runtime is there, and this is why I'm using the VC8 merge modules). Running the WiX installer (with those MSMs) succeeds on WinXP SP2, but fails on SP1 (installation stops with the error message I mentionned in my previous email). The same installer without the VC8 merge modules runs on both SP1 and SP2, so my guess is that the problem is related to using the merge modules ; I suspect this is not supported on WinXP SP1 unless the user upgrades Windows Installer (maybe I'm wrong, I'm new to MSI stuff to be honest...). So sure linking the VC8 Runtime statically would help (no need to use the VC8 MSMs - no installer problem anymore), but I really do not like that solution (modify the installed software's build process to workaround an installer issue) and that would make the VC8 MSMs completely useless (which I doubt). What I would like the installer to do is detect the version of Windows Installer and if it's too old ask the user to upgrade. Is this possible ? Best regards, Rod. Rob Mensching wrote: Either statically link against the VC8 Runtime or move to a Runtime that is available on all platforms you care about. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rod Sent: Friday, December 01, 2006 13:37 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Detect Windows installer version... Hello, I have trouble running my WiX installer on Windows XP SP1 (it runs fine on SP2). It fails with the following error message: There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. I tested a few different WiX-generated installers and I suspect the problem is related to: - the vc8-redistributable-dlls MSMs I linked with the installer - the Windows Installer version (IIRC, 2.1 on SP1, and 3.0 on SP2) What is the best solution for this problem and how to implement it ? I tried to find info about how to detect the Windows Installer version but didn't find anything. Thanks in advance, Rod - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] File attributes - how to set Archive bit?
This brings up a question that occurs to me fairly regularly reading this list and that is is it hard to be a contributor to the wix effort and/or does it take a long time to see contributed changes become available? This seems like the kind of candidate question where it'd be nice to recommend Lorne (if willing) add support for Archive to the File tag instead of doing the work in a custom action. Also a good time for another shout out to Rob/Bob and all the rest for all the great work and great support/help they do/give. We seem to have burdened so few with so much on this project. One more thing I've been curisous about is is there much interest among the readers here in springing up an effort to add external UI to this project. I've been contemplating what it would be like to be able to define the UI in html/xaml. From: [EMAIL PROTECTED] on behalf of Rob Mensching Sent: Tue 11/28/2006 3:05 PM To: Lorne Laliberte; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] File attributes - how to set Archive bit? It's a strange requirement and you'll have to use a CustomAction. You might look at the secureobj.cpp code to see how best to do that since SecureObj can change things that were just installed. Non-trivial amount of work to do correctly. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lorne Laliberte Sent: Tuesday, November 28, 2006 14:58 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] File attributes - how to set Archive bit? Thanks Mike. I'm not using the attribute directly, but I do need to be able to clear or set it. This is for an internal project so I'm not sure what I can say publically, but one of the requirements is control over all of the destination file attributes. ...Lorne Laliberte -Original Message- From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 28, 2006 4:47 PM To: Lorne Laliberte; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] File attributes - how to set Archive bit? As far as I know, the Archive bit is typically only used by backup applications to determine if a file has changed since the last time it was backed up. The OS automatically sets the archive bit when files are modified. Backup tools clear it when the file has been backed up. If you're trying to give any other semantics to the Archive bit, the OS will break them. I believe, but haven't checked, that the Archive bit will therefore be set for any files created or modified by Windows Installer during an installation. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lorne Laliberte Sent: 28 November 2006 22:11 To: wix-users@lists.sourceforge.net Subject: [WiX-users] File attributes - how to set Archive bit? Hello list! How do you set the Arhive attribute for a file? File has ReadOnly, Hidden, and System XML attributes...but Archive is rejected by candle.exe. The MSI file table doesn't offer any suggestions either. Do we need to use a custom action to do this? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FW: Background color (and other settings) for a Dialog
Have you had success with this approach? I've never been able to get the background bitmap to stay behind all the other controls once users started clicking around in the dialog. It always seems that eventually one or more of them gets z-ordered behind the bitmap and disappears on me... From: [EMAIL PROTECTED] on behalf of Bob Arnson Sent: Thu 11/23/2006 12:08 PM To: [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Background color (and other settings) for a Dialog Adrian Alonso wrote: How can I set the background color (and other settings) for a Dialog? Dialogs get their background color from Windows. If you want to change it, the easiest way is to use a bitmap that covers the entire dialog. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Detect Windows installer version...
This error is code 1723. It indicates that there was a problem running a custom action implemented in a DLL. In your case we're assuming that since it runs on one service pack but not another, that there's some dependency that a custom action relies on which isn't present on that version. I note that the SxsUninstallCA.DLL in the VC8 merge module uses the MsiEnumProductsEx API. (I extracted SxsUninstallCA from the Binary table of Microsoft_VC80_CRT_x86.msm using Orca and examined it using Depends.exe.) This API was added in Windows Installer 3.0, so version 3.0 is required for using the VC8 redistributable MSMs. You should set the Package/@InstallerVersion attribute to 300 to ensure that at least version 3.0 of Windows Installer is installed. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rod Sent: 02 December 2006 16:36 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Detect Windows installer version... Hello, Thanks a lot for your answer. But... hmmm... I'm not sure my message clearly described my problem. The installed software runs on both WinXP SP1 and SP2 (provided the VC8 runtime is there, and this is why I'm using the VC8 merge modules). Running the WiX installer (with those MSMs) succeeds on WinXP SP2, but fails on SP1 (installation stops with the error message I mentionned in my previous email). The same installer without the VC8 merge modules runs on both SP1 and SP2, so my guess is that the problem is related to using the merge modules ; I suspect this is not supported on WinXP SP1 unless the user upgrades Windows Installer (maybe I'm wrong, I'm new to MSI stuff to be honest...). - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] File attributes - how to set Archive bit?
You still need the custom action, because the File table's Attributes column does not support clearing the Archive attribute. I don't think this is a particularly common thing to do - for the reasons I explained earlier - so do not think it justifies complicating the compiler, the custom actions, and the documentation. Specifically, the OS will automatically set the Archive bit when installing a new file anyway. If you clear the flag after installing the file, the file will not be backed up on the next incremental or differential backup, which will very much surprise system administrators, and could cause your software not to work correctly if the system has to be restored from the last full backup plus a differential or a sequence of incrementals (because a critical file or change to a critical file was not captured in the backup). On the whole I don't think it's a good thing to do. -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lemire Sent: 02 December 2006 17:35 To: Rob Mensching; Lorne Laliberte; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] File attributes - how to set Archive bit? This brings up a question that occurs to me fairly regularly reading this list and that is is it hard to be a contributor to the wix effort and/or does it take a long time to see contributed changes become available? This seems like the kind of candidate question where it'd be nice to recommend Lorne (if willing) add support for Archive to the File tag instead of doing the work in a custom action. Also a good time for another shout out to Rob/Bob and all the rest for all the great work and great support/help they do/give. We seem to have burdened so few with so much on this project. One more thing I've been curisous about is is there much interest among the readers here in springing up an effort to add external UI to this project. I've been contemplating what it would be like to be able to define the UI in html/xaml. _ From: [EMAIL PROTECTED] on behalf of Rob Mensching Sent: Tue 11/28/2006 3:05 PM To: Lorne Laliberte; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] File attributes - how to set Archive bit? It's a strange requirement and you'll have to use a CustomAction. You might look at the secureobj.cpp code to see how best to do that since SecureObj can change things that were just installed. Non-trivial amount of work to do correctly. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lorne Laliberte Sent: Tuesday, November 28, 2006 14:58 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] File attributes - how to set Archive bit? Thanks Mike. I'm not using the attribute directly, but I do need to be able to clear or set it. This is for an internal project so I'm not sure what I can say publically, but one of the requirements is control over all of the destination file attributes. ...Lorne Laliberte -Original Message- From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 28, 2006 4:47 PM To: Lorne Laliberte; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] File attributes - how to set Archive bit? As far as I know, the Archive bit is typically only used by backup applications to determine if a file has changed since the last time it was backed up. The OS automatically sets the archive bit when files are modified. Backup tools clear it when the file has been backed up. If you're trying to give any other semantics to the Archive bit, the OS will break them. I believe, but haven't checked, that the Archive bit will therefore be set for any files created or modified by Windows Installer during an installation. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lorne Laliberte Sent: 28 November 2006 22:11 To: wix-users@lists.sourceforge.net Subject: [WiX-users] File attributes - how to set Archive bit? Hello list! How do you set the Arhive attribute for a file? File has ReadOnly, Hidden, and System XML attributes...but Archive is rejected by candle.exe. The MSI file table doesn't offer any suggestions either. Do we need to use a custom action to do this? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Strange error
That error is thrown when an included file uses a prefix that is not declared in the parent file. I'm adding code to properly identify and report the error; it should be in the next release after Monday. From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Fredrik Grohn [EMAIL PROTECTED] Sent: Saturday, December 02, 2006 5:09 PM To: 'Mike Dimmick'; 'Probir Chatterjee'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Strange error I don’t know much about the error in question here, sorry. However I noticed a different problem with the code in this example; the File element should not have a SelfRegCost attribute set. This would cause the DLL to be registered twice possibly resulting in unexpected behavior during runtime. Fredrik From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: Friday, November 10, 2006 12:27 AM To: 'Probir Chatterjee'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Strange error That error message appears to be erroneously produced for any invalid XML: the catch handler in Preprocessor.cs which catches XmlException on loading the document (line 258) reports SP1ProbablyNotInstalled (error 147). You might try adding the pca namespace to your root document's WiX element. Alternatively, convert your Includes to Fragments. Place your components under a DirectoryRef element. Then, remove the ?Include? directives from your main .wxs file, compile the Fragments separately, and link them all together with light (specifying each .wixobj you need). CWXCom.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi; xmlns:pca=http://schemas.microsoft.com/wix/2005/02/pubca; Fragment DirectoryRef Id=TARGETDIR Component Id=MyCOM_dll DiskId=1 Guid=DB37D412-2DA6-46b8-866C-5FFA67163B17 File Id=MyCOM_dll Name=CWXBus_1.dll LongName=CWXBusinessRulesII.dll src=..\..\CWXBusinessRulesII\CWXBusinessRulesII.dl KeyPath=yes Vital=yes SelfRegCost=1 / pca:ComPlusApplication Id=MyCOM Name=My COM+ Application pca:ComPlusAssembly Id=MyComPlusAssembly Type=native DllPath=[#MyCOM_dll] pca:ComPlusComponent Id=MyCOM CLSID=8BAC1633-E462-4f56-97EF-E2D48BA61916 / /pca:ComPlusAssembly /pca:ComPlusApplication /Component /DirectoryRef /Fragment /Wix VS2005 has just told me that Component is not valid under Include according to the schema. The schema validation may be what’s causing the XmlException. I’m not sure why Component isn’t allowed when File and Registry are – surely this is also a bug? -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Probir Chatterjee Sent: 09 November 2006 07:58 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Strange error Importance: High Hi Everyone, I am trying to create an installer using WIX and it has started giving me strange problems. I need to install 2 websites, 1 webservice, 1 db and a COM component. I could do the 1st four without any problem, but when tried putting in the code for COM component I have run into a strange problem On running candle.exe, I am receiving this error: Candle.exe : error CNDL0147 : An error has occurred that most likely indicates that .NET framework 1.1 Service Pack 1 has not been installed. Please see the following website for more information about the service pack and how to install it : http://support.microsoft.com/?kbid=867460 I have installed .net framework 1.1 sp1 but the problem won’t go away I am using the following file for candle and light: d:\tools\wix-2.0.4415.0-binaries\candle.exe cwx_arabic.wxs -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext d:\tools\wix-2.0.4415.0-binaries\light.exe -out cwx_arabic.msi cwx_arabic.wixobj D:\tools\wix-2.0.4415.0-binaries\wixui.wixlib D:\tools\wix-2.0.4415.0-binaries\sca.wixlib -loc D:\tools\wix-2.0.4415.0-binaries\WixUI_en-us.wxl D:\tools\wix-2.0.4415.0-binaries\pubca.wixlib -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext The code for my CWXCom.wxi looks like the following: ?xml version='1.0' encoding='UTF-8'? Include xmlns=http://schemas.microsoft.com/wix/2003/01/wi; xmlns:pca=http://schemas.microsoft.com/wix/2005/02/pubca; Component Id=MyCOM_dll DiskId=1 Guid=DB37D412-2DA6-46b8-866C-5FFA67163B17 File Id=MyCOM_dll Name=CWXBus_1.dll LongName=CWXBusinessRulesII.dll src=..\..\CWXBusinessRulesII\CWXBusinessRulesII.dl KeyPath=yes Vital=yes SelfRegCost=1 / pca:ComPlusApplication Id=MyCOM Name=My COM+ Application pca:ComPlusAssembly Id=MyComPlusAssembly Type=native DllPath=[#MyCOM_dll] pca:ComPlusComponent Id=MyCOM CLSID=8BAC1633-E462-4f56-97EF-E2D48BA61916 / /pca:ComPlusAssembly /pca:ComPlusApplication /Component /Include The main .wxs file refers the component as follows (I am only copy pasting the sections where the file is
