[WiX-users] Cabinet file dates are stored in local time rather than UTC
Hi Guys I'm having this issue where creating an installer in Australia and having it available for download in the US causes WPF images to be unable to be generated. The cause we have determined is that the modified date of the assemblies is in the future due to the Cabbing process storing the file timestamps in local rather than UTC. We are on WiX 3. Has anybody else noticed this behavior? And would anybody be able to help me modify the source? I am finding it hard to find information on the winterop.dll CreateCabAddFile which appears to be the native function used by WiX. I found this CodeProjecthttp://www.codeproject.com/KB/files/CABCompressExtract.aspx?display=Printarticle specifying the option of local or UTC for cabinet files, but that is about all. Granted this issue only shows itself within the first 24 hours of a release, it is annoying none-the-less. Cheers Matthew Rowan -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] domain name
Hi Lindsay, I just use a VBScript custom action. ' Set Short Domain Name Set objSysInfo = CreateObject(ADSystemInfo) Session.Property(P_APP_DOMAIN) = objSysInfo.DomainShortName Hope this helps. -Matthew Rowan On 3/9/07, Lindsay Harris [EMAIL PROTECTED] wrote: Hi, I was wondering, is there an easy way to get the domain name of the target machine in wix? Thanks! Lindsay Harris - 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] Bootstrapper
To do that I need to conditionally set the command line arguments with REINSTALLMODE=vomus REINTALL=all when the product is already installed. Does anybody know how to do that using the Visual Studio 2005 GenerateBootstrapper task? -Matthew Rowan -Original Message- From: Stefan Pavlik [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 February 2007 20:29 To: Matthew Rowan Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper Hi again... Matthew Rowan wrote: Thanks for the quick reply Stefan. What I have found is that when I build a new installer for the next minor version it does not launch in Maintenance mode because the package code is different, but the product code is the same and I get the error message Another version of this product is already installed. Installation of this version cannot continue, when using just the msi or the Visual Studio bootstrapper. Do you have your Bootstrapper to always launch with the Reinstall properties set when the product code is detected to be installed? However, I would have thought that would always do a reinstall then and not allow maintenance mode. My bootstrapper works in following way: If the product is already installed then the installer is launched with REINSTALLMODE=vomus REINTALL=all So if the package code is the same it will run the Maintenance mode and if the package code is different it will run reinstallation. In fact I do not use the Resume dialog for reinstallation. The Maintenance mode is started in both cases, so the user needs to press the Reinstall (repair) button in order to start reinstallaion. Regards Stefan Cheers, -Matthew Rowan -Original Message- From: Stefan Pavlik [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 February 2007 17:24 To: Matthew Rowan Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper Hi Matthew,... I have, personaly, no experience with the Visual Studio 2005 Bootstrapper but the simple bootstrapper I use (wrote) does not have the step 6 you are writing about. It is simply not needed because when you run the maintenance mode with arguments REINSTALLMODE=vomus REINSTALL=ALL it will do what you want. It is simply because the 'v' option of REINSTALLMODE means 'runs from source and recaches local package'. Regards Stefan Matthew Rowan wrote: Hi All, I know this topic has been of much discussion and I have looked through all of the previous mailings but am still unable to produce what I need. All I want is a bootstrapper that is similar to InstallShield to perform minor upgrades. I need to: 1. Ensure prerequisites are present and if not then install (.NET 2.0, Windows Installer 3.1) 2. Get the product code of the package. 3. Check if the product code is already installed. 4. If it isn't, launch the install normally. 5. If it is and the package code is the same, launch maintenance mode. 6. If the package code is different, launch the install in reinstall mode. Preferably I would like to display a splash screen while the bootstrapper fires up msiexec. Almost all the requirements are handled very nicely by the Visual Studio 2005 GenerateBootstrapper task and is the preferred solution, however it does not handle requirement 6. Changing the product code would resolve this, but then I need to mess with my msi and schedule RemoveExistingProducts near the end of the install to maintain settings in files like the web.config, as far as I know. Is this the recommended action? It is direction I'm leaning towards. The other option using the Bootstrapper at http://sourceforge.net/tracker/?group_id=105970atid=654188 and modifying it with msistuff.exe setup.exe /o INSTALLUPD /d mymsi.msi /b mymsi.msi /v 200 /n My Product. Using this requirements 1 and 5 aren't satisfied. Another option I have read is to use the GenerateBootstrapper task to launch a C# UI and check everything with that. But this sounds like a lot of unnecessary work and I don't know how to go about this. Also with either bootstrapper option I have tried the Visual Styles of my installer are gone. This is a minor issue except that the ComboBox drop down list do not show (you have to use the up and down keys to go through the options). Has anyone else experienced this? Thanks, -Matthew Rowan - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users
[WiX-users] Bootstrapper
Hi All, I know this topic has been of much discussion and I have looked through all of the previous mailings but am still unable to produce what I need. All I want is a bootstrapper that is similar to InstallShield to perform minor upgrades. I need to: 1. Ensure prerequisites are present and if not then install (.NET 2.0, Windows Installer 3.1) 2. Get the product code of the package. 3. Check if the product code is already installed. 4. If it isn't, launch the install normally. 5. If it is and the package code is the same, launch maintenance mode. 6. If the package code is different, launch the install in reinstall mode. Preferably I would like to display a splash screen while the bootstrapper fires up msiexec. Almost all the requirements are handled very nicely by the Visual Studio 2005 GenerateBootstrapper task and is the preferred solution, however it does not handle requirement 6. Changing the product code would resolve this, but then I need to mess with my msi and schedule RemoveExistingProducts near the end of the install to maintain settings in files like the web.config, as far as I know. Is this the recommended action? It is direction I'm leaning towards. The other option using the Bootstrapper at http://sourceforge.net/tracker/?group_id=105970atid=654188 and modifying it with msistuff.exe setup.exe /o INSTALLUPD /d mymsi.msi /b mymsi.msi /v 200 /n My Product. Using this requirements 1 and 5 aren't satisfied. Another option I have read is to use the GenerateBootstrapper task to launch a C# UI and check everything with that. But this sounds like a lot of unnecessary work and I don't know how to go about this. Also with either bootstrapper option I have tried the Visual Styles of my installer are gone. This is a minor issue except that the ComboBox drop down list do not show (you have to use the up and down keys to go through the options). Has anyone else experienced this? Thanks, -Matthew Rowan - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.0 and Votive?
I am also interested in moving to WiX v3 from v2. I already have a wixproj file I am maintaining for SharpDevelop and would like to move this into Visual Studio. The only thing I am cautious of is that I will need to do patch creation and on http://wix.sourceforge.net/faq.html it has What's New in WiX v3 ... Patch creation support (soon). Is this still the case, or is patch creation in WiX v3 possible? Regards, -Matthew Rowan - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding records to MSI on the fly
I am trying to allow users to select which WebSite they wish to install a virtual directory under. I have used the method describe here which gives me the list however the virtual directory is still installed under the default web site since the port of the Web Address is the same. This is my declaration of the web site as is stated in the WiX help. Nesting WebSite under Product, Fragment, or Module results in a web site locator record being created in the IIsWebSite table. This means that the web site itself is neither installed nor uninstalled by the MSI package. It does make the database available for referencing from a WebApplication, WebVirtualDir or WebDir record. This allows an MSI to install WebApplications, WebVirtualDirs or WebDirs to already existing web sites on the machine. The install will fail if the web site does not exist in these cases. WebSite Id=DefaultWebSite Description=[TARGETWEBCOMBO] WebAddress Id=AllUnassigned Port=80 / /WebSite and under a component I reference this Web Site WebVirtualDir Id=VirtualDir Alias=[P_IIS_VIRTUALDIRECTORY] Directory=DirWeb WebSite=DefaultWebSite WebApplication Id=WebApp Name=[P_IIS_VIRTUALDIRECTORY] /WebApplication /WebVirtualDir Any help on what I need to do would be greatly appreciated. Regards, -Matthew Rowan On 2/2/07, carlldev [EMAIL PROTECTED] wrote: I found an article somewhere that states that the values in the tables that were there when the MSI started cannot be removed or updated. Removing the Listitem from the Combobox also didn't work because that dropped the whole table all together as there are no other comboboxes. So I figured out 2 ways of doing it: 1. Orca By editing the MSI with Orca I was able to remove the offending value from the Combobox table. 2. This causes an ICE17 warning but it still compiles I removed the combobox Listitems from the combobox I want to populate and created a separate combobox with width and height = 0 (to make it invisible). I gave this dummy combobox 1 Listitem to force the creation of the Combobox table. I also tried doing a create table query to get create the required Combobox table but can't get it to work The query looks like this: CREATE TABLE `ComboBox` (`Property` CHARACTER(72) NOT NULL, `Order` SHORT NOT NULL, `Value` CHARACTER(64) NOT NULL, `Text` CHARACTER(64) LOCALIZABLE) PRIMARY KEY `Property`, `Order` TEMPORARY if anyone know how to solve this let me know, if only to get the ICE17 warnings to go away. -- View this message in context: http://www.nabble.com/Adding-records-to-MSI-on-the-fly-tf3150241.html#a8749870 Sent from the wix-users mailing list archive at Nabble.com. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] x86 and x64 in same wxs / msi ?
I think my case is a little different since it is a .NET application and we have some third party dlls that don’t work on a 64-bit machine, so I just switch that component so they don’t install on the 64-bit machine. I don’t know when it is required specifically mark the package or components as 64-bit. I’ll need to do some more testing myself as well to verify it does work. Another option you could do though to reduce code duplication, is to separate all the differences in the WiX into a fragment and have a 64-bit and 32-bit fragment and just link in the appropriate on for each build. You’ll still have 2 msi’s but less room for error. -Matthew Rowan From: Robert Randall [mailto:[EMAIL PROTECTED] Sent: Wednesday, 7 February 2007 04:47 To: 'Matthew Rowan' Subject: RE: x86 and x64 in same wxs / msi ? Thanks. Does this allow you to have a single .msi file / database that can be used to install on multiple target OSes, both AMD64 and x86? I posted a similar question to a Microsoft list and received a “can’t do it” answer. That answer does feel wrong. Do you use a single .msi for installs to x86 and x64 targets? Thanks, Robert. From: Matthew Rowan [mailto:[EMAIL PROTECTED] Sent: Monday, February 05, 2007 7:10 PM To: Robert Randall Subject: x86 and x64 in same wxs / msi ? Hi Robert, What I have done is just setup conditions on the platform specific components to install or not dependent on the operating system. eg. Component Id=Comp DiskId=1 Guid=x-3FD7-4DB0-9BBC-2FDF305DE466 !-- Do not install on 64-Bit Windows -- ConditionNOT VersionNT64/Condition File Id=file1.dll Source=..\file1.dll / /Component Regards, -Matthew Rowan On 2/6/07, Robert Randall [EMAIL PROTECTED] wrote: The answer to this may be obvious, but I can't seem to find any direction on how to support multiple target OSes from the same package; say x86 and x64 (AMD64) versions. My hunch is there is a simple answer but I've not been able to find a sample project or How-To for this. Would one of the experts please advise on how to best handle this? I have two separate and nearly identical packages now that produce two .msi files. One for x86 and one for x64. I would prefer to have a single package (less room for mistakes that way). Thanks. Robert Randall - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 kid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] x86 and x64 in same wxs / msi ?
Hi Robert, What I have done is just setup conditions on the platform specific components to install or not dependent on the operating system. eg. Component Id=Comp DiskId=1 Guid=x-3FD7-4DB0-9BBC-2FDF305DE466 !-- Do not install on 64-Bit Windows -- ConditionNOT VersionNT64/Condition File Id=file1.dll Source=..\file1.dll / /Component Regards, -Matthew Rowan On 2/6/07, Robert Randall [EMAIL PROTECTED] wrote: The answer to this may be obvious, but I can't seem to find any direction on how to support multiple target OSes from the same package; say x86 and x64 (AMD64) versions. My hunch is there is a simple answer but I've not been able to find a sample project or How-To for this. Would one of the experts please advise on how to best handle this? I have two separate and nearly identical packages now that produce two .msi files. One for x86 and one for x64. I would prefer to have a single package (less room for mistakes that way). Thanks. Robert Randall - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] stock dialog bitmaps
Hi Tom, The WixUI_Common is declared in the Common.wxs file. At the start of that fragment the Binary references to the Bitmaps are declared. So it sounds like you are not including Common.wxs, however, I would have thought you would have gotten an error if they weren't included. Hope this helps. Regards, -Matthew Rowan On 1/25/07, Thomas Svare [EMAIL PROTECTED] wrote: Hello, I forgot to mention that if I run light on my wxs with the stock libraries the bitmaps show up. Thanks, Tom -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] ] *On Behalf Of *Thomas Svare *Sent:* Wednesday, January 24, 2007 4:55 PM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] stock dialog bitmaps Hello, I've got a problem similar to an issue addressed earlier today. I reviewed the tutorial but I'm still running into problems. I'm using 2.4611 and I'm removing the license agreement dialog from WixUI_InstallDir.wxs. Candle and Lit build my new library just fine but when I try to Light my wxs referencing the new library I get: D:\temp\src\ui\wixui\installdir\WixUI_InstallDir.wxs : error LGHT0112 : Unresolved reference to symbol 'UI:WixUI_Common' in section 'Fragment:'. When I comment the UIRef Id=WixUI_Common / from WixUI_InstallDir.wxs and rebuild everything works fine except the bitmaps no longer show up on the dialogs. I tried a quick search of the list and didn't come up with anything. Does anyone have any ideas? Thanks, Tom - 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 - 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] SQL Server List in ComboBox
Thanks for all your help Albert. That was right on. Once the DEF file was linked it all worked beautifully. Cheers, -Matthew Rowan On 1/24/07, Albert van Peppen [EMAIL PROTECTED] wrote: Hi Matthew, The error you encounter is because the CA function is not exported in the DLL; in my project i forgot to add the DEF file in the linker options; just add $(TargetPath).DEF to the appropriate linker setting. (Configuration Properties - Linker - Input - Module Definition File) Rebuild and you're done.. I've updated my project for this and added a sample wxs file which runs great :-) If you wish I'll send you an update; I still haven't found where to put the files online so any suggestions are welcome :) Messageboxes in the CA are possible with ::AfxMessageBox(..) although i recommend in using the log functions instead. Regards, Albert van Peppen -- *Van:* Matthew Rowan [mailto:[EMAIL PROTECTED] *Verzonden:* woensdag 24 januari 2007 8:07 *Aan:* Albert van Peppen; wix-users@lists.sourceforge.net *Onderwerp:* Re: SQL Server List in ComboBox Thanks Albert, I'm still having some trouble I'm hoping you could please help me with. I've built the dll and added these lines to my WiX source as in the example in the C++ code you provided. Property Id=D4WSQLSERVER(local)/Property Property Id=D4WLOCALDATABASEONLY0/Property CustomAction Id=D4WFillSQLServersListbox BinaryKey=SQLMsiCA DllEntry=D4WFillSQLServersListbox / Binary Id=SQLMsiCA SourceFile=CustomActions\SQLMsiCA\Release\SQLMsiCA.dll / InstallUISequence Custom Action=D4WFillSQLServersListbox After=CostFinalizeD4WSQLSERVER = (local)/Custom /InstallUISequence Control Id=D4WFillSQLServersListbox Type=ListBox X=18 Y=106 Width=278 Height=80 Property=D4WSQLSERVER Sorted=yes / However, when I run the installer I get an error immediately as shown below: Action 16:52:03: D4WFillSQLServersListbox. Action start 16:52:03: D4WFillSQLServersListbox. Error 1723. 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. Action D4WFillSQLServersListbox, entry: D4WFillSQLServersListbox, library: C:\DOCUME~1\mrowan\LOCALS~1\Temp\MSI19E.tmp MSI (c) (E0:F8) [16:52:05:526]: Product: Zap BI Suite -- Error 1723. 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. Action D4WFillSQLServersListbox, entry: D4WFillSQLServersListbox, library: C:\DOCUME~1\mrowan\LOCALS~1\Temp\MSI19E.tmp Action ended 16:52:05: D4WFillSQLServersListbox. Return value 3. I don't know how to display a MessageBox to see if it has gotten into the function as I have seen suggested, since I don't know how to get a hWnd handle. I have been trying all day to get it to work with no avail. If you could point me to some tutorials or documentation regarding C++ custom action writing or suggest anything I'm doing wrong, it would be much appreciated. Thanks, -Matthew Rowan On 1/23/07, Albert van Peppen [EMAIL PROTECTED] wrote: Ok, new try :-) Regards, Albert van Peppen -- *Van:* Matthew Rowan [mailto:[EMAIL PROTECTED] *Verzonden:* maandag 22 januari 2007 23:49 *Aan:* Albert van Peppen *Onderwerp:* Re: Sorry, actually that may not work either. If you just rename it to something like sample.zip.rename , that should be enough to get through to my Gmail. Thanks, -Matthew Rowan On 1/23/07, Matthew Rowan [EMAIL PROTECTED] wrote: Thanks very much Albert, However there was no attachment on your email. I think Gmail automatically removes zip attachments. It would be greatly appreciated if you could please send it to [EMAIL PROTECTED] Thanks again, -Matthew Rowan On 1/23/07, Albert van Peppen [EMAIL PROTECTED] wrote: Hi, I've tried to send a zip to the list but this seems to be not possible :( So i send it directly to you. I t is a VC 2005.NET http://2005.net/ project with a simple CA with the requested code. In some snippets it is mentioned how to use it. If there are any problems; try to figure them out yourself and after that you can ask via the wix-user or wix-dev list ;) The code is free for use, commercial or non-commercial and is based on some snippets from along ti me ago. Greetings, Albert van Peppen Insad Grafisch b.v. - 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
Re: [WiX-users] SQL Server List in ComboBox
Thanks Albert, I'm still having some trouble I'm hoping you could please help me with. I've built the dll and added these lines to my WiX source as in the example in the C++ code you provided. Property Id=D4WSQLSERVER(local)/Property Property Id=D4WLOCALDATABASEONLY0/Property CustomAction Id=D4WFillSQLServersListbox BinaryKey=SQLMsiCA DllEntry=D4WFillSQLServersListbox / Binary Id=SQLMsiCA SourceFile=CustomActions\SQLMsiCA\Release\SQLMsiCA.dll / InstallUISequence Custom Action=D4WFillSQLServersListbox After=CostFinalizeD4WSQLSERVER = (local)/Custom /InstallUISequence Control Id=D4WFillSQLServersListbox Type=ListBox X=18 Y=106 Width=278 Height=80 Property=D4WSQLSERVER Sorted=yes / However, when I run the installer I get an error immediately as shown below: Action 16:52:03: D4WFillSQLServersListbox. Action start 16:52:03: D4WFillSQLServersListbox. Error 1723. 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. Action D4WFillSQLServersListbox, entry: D4WFillSQLServersListbox, library: C:\DOCUME~1\mrowan\LOCALS~1\Temp\MSI19E.tmp MSI (c) (E0:F8) [16:52:05:526]: Product: Zap BI Suite -- Error 1723. 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. Action D4WFillSQLServersListbox, entry: D4WFillSQLServersListbox, library: C:\DOCUME~1\mrowan\LOCALS~1\Temp\MSI19E.tmp Action ended 16:52:05: D4WFillSQLServersListbox. Return value 3. I don't know how to display a MessageBox to see if it has gotten into the function as I have seen suggested, since I don't know how to get a hWnd handle. I have been trying all day to get it to work with no avail. If you could point me to some tutorials or documentation regarding C++ custom action writing or suggest anything I'm doing wrong, it would be much appreciated. Thanks, -Matthew Rowan On 1/23/07, Albert van Peppen [EMAIL PROTECTED] wrote: Ok, new try :-) Regards, Albert van Peppen -- *Van:* Matthew Rowan [mailto:[EMAIL PROTECTED] *Verzonden:* maandag 22 januari 2007 23:49 *Aan:* Albert van Peppen *Onderwerp:* Re: Sorry, actually that may not work either. If you just rename it to something like sample.zip.rename , that should be enough to get through to my Gmail. Thanks, -Matthew Rowan On 1/23/07, Matthew Rowan [EMAIL PROTECTED] wrote: Thanks very much Albert, However there was no attachment on your email. I think Gmail automatically removes zip attachments. It would be greatly appreciated if you could please send it to [EMAIL PROTECTED] Thanks again, -Matthew Rowan On 1/23/07, Albert van Peppen [EMAIL PROTECTED] wrote: Hi, I've tried to send a zip to the list but this seems to be not possible :( So i send it directly to you. I t is a VC 2005.NET http://2005.net/ project with a simple CA with the requested code. In some snippets it is mentioned how to use it. If there are any problems; try to figure them out yourself and after that you can ask via the wix-user or wix-dev list ;) The code is free for use, commercial or non-commercial and is based on some snippets from along ti me ago. Greetings, Albert van Peppen Insad Grafisch b.v. - 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
