Re: [WiX-users] wix 3.0 weekly release symbols
We don't push the symbols because they take huge amounts of disk space. To get symbols, you'll unfortunately need to build. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of zhisheng huang Sent: Thursday, April 24, 2008 14:41 To: wix-users@lists.sourceforge.net Subject: [WiX-users] wix 3.0 weekly release symbols Hi, I am looking for wix symbols. However, I did not find it on the weekly release. Does anyone know if the symbols are available? Thanks, Zhisheng Back to work after baby- how do you know when you're ready?http://lifestyle.msn.com/familyandparenting/articleNW.aspx?cp-documentid=5797498ocid=T067MSN40A0701A - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Odd error when trying Include assembly in build
What version of the WiX toolset are you using? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Payne Sent: Thursday, April 24, 2008 11:41 To: wix-users@lists.sourceforge.net Cc: Darryl Brown Subject: [WiX-users] Odd error when trying Include assembly in build Hi, I am using Wix 3.0, and am trying to build a project which installs an assembly which depends on version 2.0 of the .NET Framework. The assembly is marked as net, and the ProcessorArchitecture is 'msil'. I have .NET framework 2.0 SP1 installed on my system. The error is d:\sa\drivers\mobilepc\auxdisplay\managedapi\setup\managedapi.wxs(17) : error LGHT0132 : The assembly file 'd:\sa.binaries.x86fre\SideShow\API\Microsoft.SideShow.dll' appears to be invalid. Please ensure this is a valid assembly file and that the user has the appropriate access rights to this file. More information: Version 2.0 is not a compatible version. Any suggestions? Thanks. --Doug - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding a component on a minor upgrade
I think the MSI SDK on Minor Upgrades confirms your observations: A minor upgrade can be used to add new features and components but cannot reorganize the feature-component tree. You'll need to add the new Components to a new Feature. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric Viollet Sent: Thursday, April 24, 2008 06:30 To: wix-users@lists.sourceforge.net Subject: [WiX-users] adding a component on a minor upgrade Hi everyone, Is it possible to add a component to an installed feature through a minor upgrade? The component I'm trying to add contains two files. And it seems, by the behavior I'm experiencing, that the answer is *no*. Could someone confirm this? Point #1: The product, to which I'd like to add a component, upgrades well if I don't add the component... Point #2: If I try to add the component, I get the following behavior: the product upgrades without apparent errors. However, none of the files are updated, the Add/Remove Programs is updated with the new version name. And when I try to uninstall the upgraded version, the entry in Add/Remove Programs is removed *but* none of the files/services are removed. Point #3: Strangely, I have another product in which I already had added a Component in an installed feature without any problem. The only difference, is that the component I added only contained any entry CreateFolder (no Files) Thanks for your help. Fred - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] questions about minor updates
1. I believe this is correct. 2. Yes, setupbld.exe is supposed to handle this correctly. It currently decides things are a minor upgrade if the major version (the first number) is the same as the installed bits and any of the other parts of the version are higher than the installed bits. This just the way it determines when to do minor upgrades. 3. I am not sure I ever tried to run the tool on Win2k. I believe the original design parameters were XP and above... Note: setupbld is a very primitive bootstrapper. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lincoln Lavoie Sent: Thursday, April 24, 2008 19:03 To: wix-users@lists.sourceforge.net Subject: [WiX-users] questions about minor updates Hello All, I've got a couple of quick questions about using WiX through the update process. 1. When you launch a minor update with the msiexec options to enable the update, this would typically be done by the setup.exe wrapper. Now, I believe I read somewhere that you shouldn't use those options for the first install. Is this correct? 2. If the above answer is yes, does the setupbld.exe wrapper in WiX 3.0 handle this problem? If not, are there any recommendations for handling this? It would seem very nasty to need 2 versions of our installer (one for clean machines and one for updates). 3. Has anyone seen issues with setupbld.exe, where it does not seem to accept any command line arguments? Even when I run it with -? is returns Error 0x80070057: Bad commandline argument: -?, mind you this is on a Windows2000pro system, I haven't tried it on an XP build environment yet. Thanks for your help. Cheers, Lincoln - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installer will not preserve the previous installed location.
Take a look at the verbose log file. It will show you the state changes of INSTALLPATH. My bet is that you'll find the Windows Installer is setting INSTALLPATH to the default during some initialization. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kai Lee Sent: Thursday, April 24, 2008 15:30 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installer will not preserve the previous installed location. Hi, Now I run into an issue related to the previous selected new location will not be populated back when I do change installation second time. The Feature's ConfigurableDirectory attribute will only allow me to change the installed location of the application first time. Feature Id=NewSuite ConfigurableDirectory=INSTALLPATH InstallDefault=local Title=New Suite Level=1... Let say I change the default location c:\Program File\NewSuite to c:\temp\NewSuite. Then I launch the installation program again and click the Modify button in the Custom Dialog screen. The New Suite feature will show up with default path c:\Program File\NewSuite and the installation program does not provide me with Browse button. Therefore, when I install some other features which will force to put into the wrong location, c:\Program File\NewSuite, instead of previous installed location c:\temp\NewSuite. Then the application stops working. Do you have any suggestion how to fix it? Many thanks, Kai Express yourself wherever you are. Mobilize!http://www.gowindowslive.com/Mobile/Landing/Messenger/Default.aspx?Locale=en-US?ocid=TAG_APRIL - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding a component on a minor upgrade
Hi Rob, Thanks for your answer. Now I'm trying to add my new Component in a new Feature. The problem is that I can't figure out where to add my Feature. At the moment, I have only one Feature, and this Feature should always be installed. The Feature I'd like to add should also always be installed. I tried adding it as a new Feature at the same level as the first Feature, and I also tried adding it as a new leaf in the first Feature. None of these configurations get my new feature to be installed. It seems that I can't install the new Feature. Here are the confs I tried: #1: Feature Id='Complete' Level='1' . a bunch of existing components /Feature Feature Id='Complete2' Level='1' ComponentRef Id='MY_NEW_COMPONENT' / /Feature #2: Feature Id='Complete' Level='1' . a bunch of existing components Feature Id='Complete2' Level='1' ComponentRef Id='MY_NEW_COMPONENT' / /Feature /Feature Any ideas? Thanks again for your help. Fred Rob Mensching a écrit : I think the MSI SDK on Minor Upgrades confirms your observations: A minor upgrade can be used to add new features and components but cannot reorganize the feature-component tree. You'll need to add the new Components to a new Feature. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric Viollet Sent: Thursday, April 24, 2008 06:30 To: wix-users@lists.sourceforge.net Subject: [WiX-users] adding a component on a minor upgrade Hi everyone, Is it possible to add a component to an installed feature through a minor upgrade? The component I'm trying to add contains two files. And it seems, by the behavior I'm experiencing, that the answer is *no*. Could someone confirm this? Point #1: The product, to which I'd like to add a component, upgrades well if I don't add the component... Point #2: If I try to add the component, I get the following behavior: the product upgrades without apparent errors. However, none of the files are updated, the Add/Remove Programs is updated with the new version name. And when I try to uninstall the upgraded version, the entry in Add/Remove Programs is removed *but* none of the files/services are removed. Point #3: Strangely, I have another product in which I already had added a Component in an installed feature without any problem. The only difference, is that the component I added only contained any entry CreateFolder (no Files) Thanks for your help. Fred - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Выгодное предложение для Агенс тв Недвижимости
Реклама в новом виде. Рассылки по электронной почте на специальных условиях только для вас (бесплатный тест). 510-72-66 - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding a component on a minor upgrade
Hi, I've done some other tests and added the MSIENFORCEUPGRADECOMPONENTRULES property in my wxs file. The results are quite surprising. In both of the configurations listed below I get the error 2771: The MSDN says that it means: Upgrade of feature [2] has a missing component. . I don't understand this message since none of the existing components have been removed. I'm only trying to add a new component in a new feature :( I'm really lost. :( Fred Frédéric Viollet a écrit : Hi Rob, Thanks for your answer. Now I'm trying to add my new Component in a new Feature. The problem is that I can't figure out where to add my Feature. At the moment, I have only one Feature, and this Feature should always be installed. The Feature I'd like to add should also always be installed. I tried adding it as a new Feature at the same level as the first Feature, and I also tried adding it as a new leaf in the first Feature. None of these configurations get my new feature to be installed. It seems that I can't install the new Feature. Here are the confs I tried: #1: Feature Id='Complete' Level='1' . a bunch of existing components /Feature Feature Id='Complete2' Level='1' ComponentRef Id='MY_NEW_COMPONENT' / /Feature #2: Feature Id='Complete' Level='1' . a bunch of existing components Feature Id='Complete2' Level='1' ComponentRef Id='MY_NEW_COMPONENT' / /Feature /Feature Any ideas? Thanks again for your help. Fred Rob Mensching a écrit : I think the MSI SDK on Minor Upgrades confirms your observations: A minor upgrade can be used to add new features and components but cannot reorganize the feature-component tree. You'll need to add the new Components to a new Feature. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric Viollet Sent: Thursday, April 24, 2008 06:30 To: wix-users@lists.sourceforge.net Subject: [WiX-users] adding a component on a minor upgrade Hi everyone, Is it possible to add a component to an installed feature through a minor upgrade? The component I'm trying to add contains two files. And it seems, by the behavior I'm experiencing, that the answer is *no*. Could someone confirm this? Point #1: The product, to which I'd like to add a component, upgrades well if I don't add the component... Point #2: If I try to add the component, I get the following behavior: the product upgrades without apparent errors. However, none of the files are updated, the Add/Remove Programs is updated with the new version name. And when I try to uninstall the upgraded version, the entry in Add/Remove Programs is removed *but* none of the files/services are removed. Point #3: Strangely, I have another product in which I already had added a Component in an installed feature without any problem. The only difference, is that the component I added only contained any entry CreateFolder (no Files) Thanks for your help. Fred - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding a component on a minor upgrade
News again The error 2771 was indeed my fault. So please don't pay attention to last message I posted. But with packages that do not raise the 2771 error, I still can't add a new feature with a new component :( Fred Frédéric Viollet a écrit : Hi, I've done some other tests and added the MSIENFORCEUPGRADECOMPONENTRULES property in my wxs file. The results are quite surprising. In both of the configurations listed below I get the error 2771: The MSDN says that it means: Upgrade of feature [2] has a missing component. . I don't understand this message since none of the existing components have been removed. I'm only trying to add a new component in a new feature :( I'm really lost. :( Fred Frédéric Viollet a écrit : Hi Rob, Thanks for your answer. Now I'm trying to add my new Component in a new Feature. The problem is that I can't figure out where to add my Feature. At the moment, I have only one Feature, and this Feature should always be installed. The Feature I'd like to add should also always be installed. I tried adding it as a new Feature at the same level as the first Feature, and I also tried adding it as a new leaf in the first Feature. None of these configurations get my new feature to be installed. It seems that I can't install the new Feature. Here are the confs I tried: #1: Feature Id='Complete' Level='1' . a bunch of existing components /Feature Feature Id='Complete2' Level='1' ComponentRef Id='MY_NEW_COMPONENT' / /Feature #2: Feature Id='Complete' Level='1' . a bunch of existing components Feature Id='Complete2' Level='1' ComponentRef Id='MY_NEW_COMPONENT' / /Feature /Feature Any ideas? Thanks again for your help. Fred Rob Mensching a écrit : I think the MSI SDK on Minor Upgrades confirms your observations: A minor upgrade can be used to add new features and components but cannot reorganize the feature-component tree. You'll need to add the new Components to a new Feature. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric Viollet Sent: Thursday, April 24, 2008 06:30 To: wix-users@lists.sourceforge.net Subject: [WiX-users] adding a component on a minor upgrade Hi everyone, Is it possible to add a component to an installed feature through a minor upgrade? The component I'm trying to add contains two files. And it seems, by the behavior I'm experiencing, that the answer is *no*. Could someone confirm this? Point #1: The product, to which I'd like to add a component, upgrades well if I don't add the component... Point #2: If I try to add the component, I get the following behavior: the product upgrades without apparent errors. However, none of the files are updated, the Add/Remove Programs is updated with the new version name. And when I try to uninstall the upgraded version, the entry in Add/Remove Programs is removed *but* none of the files/services are removed. Point #3: Strangely, I have another product in which I already had added a Component in an installed feature without any problem. The only difference, is that the component I added only contained any entry CreateFolder (no Files) Thanks for your help. Fred - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still
[WiX-users] Different herbal formula for different needs
Get the herbal remedies of your choice easily with new selections http://www.kineabej.com/ - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcut without icon
Can you post the wix code for that? Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Apr 25, 2008, at 24:19 , Riyaz Mogharabin wrote: Dear All, I Hope you are fine and doing well. I have created some shortcuts in the program files menu, and among them is a readme file. I need the shortcut to have the original icon of HTML files. But when I don't introduce an icon for it, there will be an UNKNOWN FILE TYPE icon by default. This was not like this in wix 2. How can I change this? Thank you for your help, Riyaz - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Un-installing Merge Module breaks upgraded component dependent on versioned dlls
Hi Wix-users, Another chestnut to do with shared MSM, here's the scenario: PRODUCT 1 contains: - MSM_A with contains version 1 of a backward compatible, A.dll, in component A, this depends on - MSM_B1 which contains version 1 of a non-backwards compatible, B1.dll, in component B1 PRODUCT 2 contains: - MSM_A with contains version 2 of a backward compatible, A.dll, in component A, this depends on - MSM_B2 which contains version 2 of a non-backwards compatible, B2.dll, in component B2 SCENARIO 1. Install Product 1, this installs A and B1 on the machine 2. No install Product 2, this upgrades A to version 2, and installs B2 on the machine (side by side with B1) 3. Now un-install Product 2, this removed B2 but leaves A with the upgraded version. Using A.dll now FAILS as it required B2, but only has B1 installed. Note that, to complicate matters, the dlls A, B1 and B2 are all COM (which is why Product 1 and Product 2 don't simply contain their own separate versions of A). But I think that this is a slight red-herring, though I may be wrong on this. Suggestions so far have been 1. Make B2 permanent - though this seems ugly, and results in files left on the machine after un-installing all products 2. Remove product 1 when product 2 is installed, which isn't really an option 3. Effectively changing the setup so that B1 and B2 are replaced with an upgrade component B which is upgraded in the same way as A is (though as these are shared, not backwards compatible and COM his make this option none trivial) Any help on this much appreciated. Yours, David - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Device Driver Installation
Anthony, As far as I know DIFxApp still only works with WiX 2. My workaround was to create a merge module using WiX 2 just for the driver installation and merge that into my WiX 3 installer. Regards, John _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Mahieu Sent: 25 April 2008 04:46 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Device Driver Installation Hey guys, this is my first post. I've got this relatively simple project (WiX v3, using Votive w/ VS2005) that I now need to add device driver installation to. I need to install two drivers if a specific feature is selected to be installed. From everything I'm reading, I need to use DIFxApp. Unfortunately, this is where all helpful information I've found on the web stops. I read in previous questions that DIFxApp won't work with WiX 3. Is this still the case? If so, how would one recommend going about installing drivers in WiX 3? If the issue has been resolved and DIFxApp now works with WiX 3, does anyone have a tutorial on what needs to be done to install the drivers? I know I should be looking into the DDK for some help, but I couldn't even find that (anyone have a link?). Any help someone can give me would be greatly appreciated, as I'm rather new to all this. Thanks! - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX-users Digest, Vol 23, Issue 180
Hi, This is the link you asked about. Just a hint: DIFx is part of DDK. MSDN | MSDN Library | Win32 and COM Development | Windows Driver Kit | Device Installation | Design Guide } Using Driver Install Frameworks (DIFx) Driver Install Frameworks for Applications (DIFxApp): http://msdn2.microsoft.com/en-us/library/ms790295.aspx BR Yuri Gendelman -Original Message- Message: 1 Date: Thu, 24 Apr 2008 22:45:36 -0500 From: Anthony Mahieu [EMAIL PROTECTED] Subject: [WiX-users] Device Driver Installation To: wix-users@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 Hey guys, this is my first post. I've got this relatively simple project (WiX v3, using Votive w/ VS2005) that I now need to add device driver installation to. I need to install two drivers if a specific feature is selected to be installed. From everything I'm reading, I need to use DIFxApp. Unfortunately, this is where all helpful information I've found on the web stops. I read in previous questions that DIFxApp won't work with WiX 3. Is this still the case? If so, how would one recommend going about installing drivers in WiX 3? If the issue has been resolved and DIFxApp now works with WiX 3, does anyone have a tutorial on what needs to be done to install the drivers? I know I should be looking into the DDK for some help, but I couldn't even find that (anyone have a link?). Any help someone can give me would be greatly appreciated, as I'm rather new to all this. Thanks! - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding a component on a minor upgrade
Hi Fredrick, I'm going to guess it may have something to do with the arguments for the msiexec on the minor update. The arguments specify things like, replace files only if..., etc. I would make sure there isn't one that specifies to add files/features not previously present. Cheers, Lincoln Frédéric Viollet wrote: Hi Rob, Thanks for your answer. Now I'm trying to add my new Component in a new Feature. The problem is that I can't figure out where to add my Feature. At the moment, I have only one Feature, and this Feature should always be installed. The Feature I'd like to add should also always be installed. I tried adding it as a new Feature at the same level as the first Feature, and I also tried adding it as a new leaf in the first Feature. None of these configurations get my new feature to be installed. It seems that I can't install the new Feature. Here are the confs I tried: #1: Feature Id='Complete' Level='1' . a bunch of existing components /Feature Feature Id='Complete2' Level='1' ComponentRef Id='MY_NEW_COMPONENT' / /Feature #2: Feature Id='Complete' Level='1' . a bunch of existing components Feature Id='Complete2' Level='1' ComponentRef Id='MY_NEW_COMPONENT' / /Feature /Feature Any ideas? Thanks again for your help. Fred Rob Mensching a écrit : I think the MSI SDK on Minor Upgrades confirms your observations: A minor upgrade can be used to add new features and components but cannot reorganize the feature-component tree. You'll need to add the new Components to a new Feature. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric Viollet Sent: Thursday, April 24, 2008 06:30 To: wix-users@lists.sourceforge.net Subject: [WiX-users] adding a component on a minor upgrade Hi everyone, Is it possible to add a component to an installed feature through a minor upgrade? The component I'm trying to add contains two files. And it seems, by the behavior I'm experiencing, that the answer is *no*. Could someone confirm this? Point #1: The product, to which I'd like to add a component, upgrades well if I don't add the component... Point #2: If I try to add the component, I get the following behavior: the product upgrades without apparent errors. However, none of the files are updated, the Add/Remove Programs is updated with the new version name. And when I try to uninstall the upgraded version, the entry in Add/Remove Programs is removed *but* none of the files/services are removed. Point #3: Strangely, I have another product in which I already had added a Component in an installed feature without any problem. The only difference, is that the component I added only contained any entry CreateFolder (no Files) Thanks for your help. Fred - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Can I not use directorysearch like this?
Guys We want to use directorysearch to find out if the directory selected by the user already exists. We want to set a registry to 1 if the directory exists and 0 if it does not. We thought the following wix v2 snippet would do it but it appears to not be working. Any idea why? Property Id='EXISTING_DATA_DIR' DirectorySearch Id='dsid' Depth='0' Path='..path to find'/ /Property Component ... ConditionNot EXISTING_DATA_DIR/Condition .. write existing data dir =0 into registry .. ... dir and file elements for data dir only ... /Component Component ConditionEXISTING_DATA_DIR/Condition .. write existing data dir =1 into registry .. /Component - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Release 3.0.4014.0 requires MsBuild 3.5?
Replying to my own thread here just for search archives completeness. I just installed 3.0.4025 and this issue is now resolved. Quoting history.txt: Use 2.0 MSBuild tasks instead of 3.5 - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Component sequence
I have two components that each installs a config file. Based on a
condition, only one component is run and one config file is installed.
The two source config files have different names, but I want to refer to
them using the same name in another component where I call the XmlFile and
XmlConfig to update the xml contents.
Here is my code:
Property Id=PLUGINS_PATH Value=Plugins\plugins.xml /
Property Id=USE_WCFBINDING Value=Yes/
Component Id=CompBusinessHost
Guid={4BE963AB-0290-43a1-A1E3-FC0704FE5563} KeyPath=no
File Id=File1 KeyPath=yes Name=BusinessHost.exe
Source=$(var.SourceFolder)\BusinessHost.exe /
/Component
Component Id='CompConfigFile'
Guid='{C0D7BC77-6113-49f5-B0EB-46B30FB9CB81}'
ConditionUSE_WCFBINDING~=Yes/Condition
File Id='File2' Name='BusinessHost.exe.config'
Source='$(var.SourceFolder)\BusinessHost.exe.config'/
/Component
Component Id='CompBasicHttpConfigFile'
Guid='{390B30D5-79DF-483e-91F9-68FED459F6C0}'
ConditionUSE_WCFBINDING~lt;gt;Yes/Condition
File Id='File3' Name='BusinessHost.exe.config'
Source='$(var.SourceFolder)\BusinessHostBasicHttpApp.Config' /
/Component
Component Id='CompConfigFile' Guid='{9A391F9F-B275-45e3-BF25-B87ADBABF621}'
KeyPath='yes'
util:XmlFile
Id=PluginsPath
File=[VBusInstalldir]BusinessHost.exe.config
Action=setValue
ElementPath=/configuration/appSettings/[EMAIL
PROTECTED]'pluginsPath'[\]]/@value
Value=[PLUGINS_PATH]
/
/Component
If I skip util:XmlFile, everything works fine.
BusinessHostBasicHttpApp.Config is installed with the correct name,
BusinessHost.exe.config.
But if I enable util:XmlFile, and specify USE_WCFBINGING=NO, I get an
error message:
Failed to open XML file C:\Program Files\VBus\BusinessHost.exe.config.
system error: -2147024786
It seems that CompConfigFile is run before CompBasicHttpConfigFile. Is
there a way to specify the sequence of the components??
Thanks for any advice.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Device Driver Installation
Well, I've downloaded WiX 2 and I'm going to create a merge module for my device drivers that I will merge into my WiX 3 installer. My big issue now is, where can I find the Windows DDK so I can use DIFxApp with WiX? I know this probably isn't the place to ask, but I'm guessing someone here has used it and knows where it can be found. The Microsoft site is pointing me to Microsoft Connect and MSDN, neither of which are turning up anything for me. Does the DDK need to be purchased? If so, is there any way to obtain the DIFxApp/WiX stuff for free (as that's all I need)? I should mention, we're only supporting WinXP SP2 or greater, if that makes a difference in terms of which DDK I need. Thanks for the help so far, it's really appreciated. Tony On Fri, Apr 25, 2008 at 6:04 AM, John Hall [EMAIL PROTECTED] wrote: Anthony, As far as I know DIFxApp still only works with WiX 2. My workaround was to create a merge module using WiX 2 just for the driver installation and merge that into my WiX 3 installer. Regards, John -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Anthony Mahieu *Sent:* 25 April 2008 04:46 *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] Device Driver Installation Hey guys, this is my first post. I've got this relatively simple project (WiX v3, using Votive w/ VS2005) that I now need to add device driver installation to. I need to install two drivers if a specific feature is selected to be installed. From everything I'm reading, I need to use DIFxApp. Unfortunately, this is where all helpful information I've found on the web stops. I read in previous questions that DIFxApp won't work with WiX 3. Is this still the case? If so, how would one recommend going about installing drivers in WiX 3? If the issue has been resolved and DIFxApp now works with WiX 3, does anyone have a tutorial on what needs to be done to install the drivers? I know I should be looking into the DDK for some help, but I couldn't even find that (anyone have a link?). Any help someone can give me would be greatly appreciated, as I'm rather new to all this. Thanks! - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005
Can a Votive expert help me with this? At the moment, it appears that Votive does not support the UI extension WixUI_InstallDir, but I would be happy to be proven wrong. I am using 2.0. I need to include a localization XML file for WixUI_InstallDir, but I can find no way to accomplish this entirely within Visual Studio. Is there some way to change the light.exe command-line flags WITHIN Visual Studio or the various XML files involved? Does the Votive installation include these XML files or do I ALSO need to install Wix separately? I need to add: -loc C:\Program Files\wix-2.0.5805\WixUI_en-us.wxl or the equivalent within Visual Studio. I don't want to have a parallel build system outside Visual Studio. -Jon Andersen Guardian Team: Securing CPS Citrix Systems, Inc (954) 940-7737 or x27737 This email was sent using RTST Outlook. From: Jon Andersen Sent: Thursday, April 24, 2008 4:15 PM To: 'Mark Line'; 'Willie Burton' Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 Is there some way to tie in the localization XML file using the Visual Studio plug in? I haven't been using makefiles, etc. -Jon Andersen Guardian Team: Securing CPS Citrix Systems, Inc (954) 940-7737 or x27737 This email was sent using RTST Outlook. From: Mark Line [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 2:44 PM To: Jon Andersen; 'Willie Burton' Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 Your need something like this: light -nologo -out myMSI.msi sca.wixlib, wixca.wixlib, and WixUI.wixlib C:\Program Files\wix-2.0.5805\wixui.wixlib -loc C:\Program Files\wix-2.0.5805\WixUI_en-us.wxl From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Andersen Sent: 24 April 2008 07:40 PM To: Willie Burton Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 I'm using Wix 2.0. Currently my references listed are sca.wixlib, wixca.wixlib, and WixUI.wixlib. -Jon From: Willie Burton [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 2:37 PM To: Jon Andersen Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 Did you add the WixUIExtension.dll reference? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Andersen Sent: Thursday, April 24, 2008 2:33 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 I'm trying to use WixUI_InstallDir inside Visual Studio 2005 (with integration installed) and have run into an issue. Apparently the light linker needs to be given a localization XML file, but I can't figure out how to give it to it. The error message is: light.exe : error LHGT0122: The localization string 'WixUIOK' is unknown. Ensure that the localization variable $(loc.WixUIOK) is defined. (followed by many other similar error messages). The tutorial suggests setting the Culture property of the Linker in the project properties; however, I can't find that property. Any suggestions? Thanks, -Jon - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Release 3.0.4014.0 requires MsBuild 3.5?
Seems I jumped the gun a little on this one. Issue in 3.0.4025.0: - The first time VS builds my Wix project, all goes well (= improvement over previous drop). - The second time the same VS process builds the same Wix project (without restarting VS) I get the following exception: Error 1 The build was aborted because of an internal failure. Microsoft.Build.Shared.InternalErrorException: Internal MSBuild Error: Project shouldn't be in ProjectManager already. at Microsoft.Build.Shared.ErrorUtilities.ThrowInternalError(Boolean showAssert, String unformattedMessage, Object[] args) at Microsoft.Build.BuildEngine.Engine.BuildProject(Project project, String[] targetNames, IDictionary targetOutputs, BuildSettings buildFlags, Boolean fireProjectStartedFinishedEvents) C:\Source\StingModules\AddinModule\AddinModule.csproj 0 1 SixEdgeSetupWix Seems some in process state (in the MsBuild ProjectManager) remains between builds. I have also gotten this build output error on the second build: Unhandled Exception:The build was aborted because of an unexpected logger failure. Error: The build was aborted because of an unexpected logger failure. As before, I'm using .NET FW 2.0 SP1. /M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Holmgren Mathias Sent: den 25 april 2008 16:47 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Release 3.0.4014.0 requires MsBuild 3.5? Replying to my own thread here just for search archives completeness. I just installed 3.0.4025 and this issue is now resolved. Quoting history.txt: Use 2.0 MSBuild tasks instead of 3.5 - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Device Driver Installation
You need to join a specific connect programme, it is not very easy to find your way around but it won't cost you any money. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Mahieu Sent: 25 April 2008 16:20 To: wix-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [WiX-users] Device Driver Installation Well, I've downloaded WiX 2 and I'm going to create a merge module for my device drivers that I will merge into my WiX 3 installer. My big issue now is, where can I find the Windows DDK so I can use DIFxApp with WiX? I know this probably isn't the place to ask, but I'm guessing someone here has used it and knows where it can be found. The Microsoft site is pointing me to Microsoft Connect and MSDN, neither of which are turning up anything for me. Does the DDK need to be purchased? If so, is there any way to obtain the DIFxApp/WiX stuff for free (as that's all I need)? I should mention, we're only supporting WinXP SP2 or greater, if that makes a difference in terms of which DDK I need. Thanks for the help so far, it's really appreciated. Tony On Fri, Apr 25, 2008 at 6:04 AM, John Hall [EMAIL PROTECTED] wrote: Anthony, As far as I know DIFxApp still only works with WiX 2. My workaround was to create a merge module using WiX 2 just for the driver installation and merge that into my WiX 3 installer. Regards, John _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Mahieu Sent: 25 April 2008 04:46 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Device Driver Installation Hey guys, this is my first post. I've got this relatively simple project (WiX v3, using Votive w/ VS2005) that I now need to add device driver installation to. I need to install two drivers if a specific feature is selected to be installed. From everything I'm reading, I need to use DIFxApp. Unfortunately, this is where all helpful information I've found on the web stops. I read in previous questions that DIFxApp won't work with WiX 3. Is this still the case? If so, how would one recommend going about installing drivers in WiX 3? If the issue has been resolved and DIFxApp now works with WiX 3, does anyone have a tutorial on what needs to be done to install the drivers? I know I should be looking into the DDK for some help, but I couldn't even find that (anyone have a link?). Any help someone can give me would be greatly appreciated, as I'm rather new to all this. Thanks! - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Localizing properties in WiX 2.0
Hi all, I'm trying to localize a property so when I generate a MST that property is correctly localized. I've read through the tutorial which specifically mentions localizing strings that are part of dialogs. What I'm trying to localize a string that will appear before any dialog is shown (in a simple message box). Here's what I tried to do: 1) In the installer.wxs project I set the relevant property to: Property Id=PREVENT_DOWNGRADE![CDATA[New version is already installed. Click OK to exit.]]/Property 2) Modified the WiXUI language file (WixUI_de-de.wxl) by adding: String Id=PREVENT_DOWNGRADEThis is the German text for downgrades./String I'm pretty sure it's not working because I'm including the locale in the WiXUI language file. Can someone confirms this and what's the correct way to do this? 3) Compile: candle.exe installer.wxs -dlanguageCode=1031 -dcodePage=1252 Build: light.exe -b C:\WiX\bin -out bin\mymsi_de-de.msi installer.wixobj MAIN\ui\WixUI_custom.wixlib -loc MAIN\ui\WixUI_de-de.wxl Opening the German installer (mymsi_de-de.msi) still has the English string. Any ideas would be greatly appreciated. Thanks, Alex G. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] The Component element contains an unexpected attribute
Dear list, I'm using: Microsoft Windows Vista Pro Microsoft Windows Driver Kit 6000 Microsoft Visual Studio 2008 Windows Installer XML v3 (3.0.4025.0) I have this files living in the project dir: Product.wxs DIFxApp.dll DIFxApp.wixlib DIFxAppA.dll I also have a reference to the DIFxApp.wixlib in the project solution explorer. Under References. I'm geting this errors when I try to 'candle' my setup project. Any idea??: -- Rebuild All started: Project: setup, Configuration: Debug Any CPU -- C:\Program Files\Windows Installer XML v3\bin\candle.exe -dDebug -dDevEnvDir=C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\\ -dSolutionDir=C:\code\popapp\ -dSolutionExt=.sln -dSolutionFileName=popapp.sln -dSolutionName=popapp -dSolutionPath=C:\code\popapp\popapp.sln -out obj\Debug\Product.wixobj Product.wxs C:\code\popapp\setup\Product.wxs(20,0): error CNDL0004: The Component element contains an unexpected attribute 'DriverForceInstall'. C:\code\popapp\setup\Product.wxs(20,0): error CNDL0004: The Component element contains an unexpected attribute 'DriverSequence'. C:\code\popapp\setup\Product.wxs(20,0): error CNDL0004: The Component element contains an unexpected attribute 'DriverLegacy'. Done building project setup.wixproj -- FAILED. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Localizing properties in WiX 2.0
Wouldn't you need to change your code to: Property Id=PREVENT_DOWNGRADE$(loc. PREVENT_DOWNGRADE)/Property Jim Williams -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex G Sent: Friday, April 25, 2008 9:42 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Localizing properties in WiX 2.0 Hi all, I'm trying to localize a property so when I generate a MST that property is correctly localized. I've read through the tutorial which specifically mentions localizing strings that are part of dialogs. What I'm trying to localize a string that will appear before any dialog is shown (in a simple message box). Here's what I tried to do: 1) In the installer.wxs project I set the relevant property to: Property Id=PREVENT_DOWNGRADE![CDATA[New version is already installed. Click OK to exit.]]/Property 2) Modified the WiXUI language file (WixUI_de-de.wxl) by adding: String Id=PREVENT_DOWNGRADEThis is the German text for downgrades./String I'm pretty sure it's not working because I'm including the locale in the WiXUI language file. Can someone confirms this and what's the correct way to do this? 3) Compile: candle.exe installer.wxs -dlanguageCode=1031 -dcodePage=1252 Build: light.exe -b C:\WiX\bin -out bin\mymsi_de-de.msi installer.wixobj MAIN\ui\WixUI_custom.wixlib -loc MAIN\ui\WixUI_de-de.wxl Opening the German installer (mymsi_de-de.msi) still has the English string. Any ideas would be greatly appreciated. Thanks, Alex G. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/j avaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Localizing properties in WiX 2.0
Oops, sorry, I meant (without the extraneous blank character): Property Id=PREVENT_DOWNGRADE$(loc.PREVENT_DOWNGRADE)/Property Note, you would then also need an English translation .wxl file as well for English strings. Jim From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Williams Sent: Friday, April 25, 2008 10:48 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Localizing properties in WiX 2.0 Wouldn't you need to change your code to: Property Id=PREVENT_DOWNGRADE$(loc. PREVENT_DOWNGRADE)/Property Jim Williams -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex G Sent: Friday, April 25, 2008 9:42 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Localizing properties in WiX 2.0 Hi all, I'm trying to localize a property so when I generate a MST that property is correctly localized. I've read through the tutorial which specifically mentions localizing strings that are part of dialogs. What I'm trying to localize a string that will appear before any dialog is shown (in a simple message box). Here's what I tried to do: 1) In the installer.wxs project I set the relevant property to: Property Id=PREVENT_DOWNGRADE![CDATA[New version is already installed. Click OK to exit.]]/Property 2) Modified the WiXUI language file (WixUI_de-de.wxl) by adding: String Id=PREVENT_DOWNGRADEThis is the German text for downgrades./String I'm pretty sure it's not working because I'm including the locale in the WiXUI language file. Can someone confirms this and what's the correct way to do this? 3) Compile: candle.exe installer.wxs -dlanguageCode=1031 -dcodePage=1252 Build: light.exe -b C:\WiX\bin -out bin\mymsi_de-de.msi installer.wixobj MAIN\ui\WixUI_custom.wixlib -loc MAIN\ui\WixUI_de-de.wxl Opening the German installer (mymsi_de-de.msi) still has the English string. Any ideas would be greatly appreciated. Thanks, Alex G. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/j avaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX Build Bug?
I've downloaded the latest WiX source package. I've got Visual Studio 2008 Pro from MSDN ( SW_DVD9_Visual_Studio_Pro_2008_English_Core_MLF_X14-26326.ISO ) and the latest Server 2008 PSDK installed aswell as the latest beta NAnt build. I try to run make.bat and I get the following error. When I look in the registry I have a Setup key with 12 subkeys... none of which are the ones the build script is looking for. C:\wix3-sourcesmake NAnt 0.86 (Build 0.86.2962.0; nightly; 2/10/2008) Copyright (C) 2001-2008 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///C:/wix3-sources/wix.build Target framework: Microsoft .NET Framework 2.0 Target(s) specified: inc [property] Read-only property dir.src.dutil cannot be overwritten. [readregistry] Registry Path Not Found! - key='SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VS\VSDB\';hive='Microsoft.Win32.RegistryHive[]'; [readregistry] Registry Path Not Found! - key='SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VS\VSTD\';hive='Microsoft.Win32.RegistryHive[]'; [readregistry] Registry Path Not Found! - key='SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VS\VSTS\';hive='Microsoft.Win32.RegistryHive[]'; [readregistry] Registry Path Not Found! - key='SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VS\VSTT\';hive='Microsoft.Win32.RegistryHive[]'; [echo] VS Test Tools are installed. The Tests will be built. prereqcheck: BUILD FAILED - 4 non-fatal error(s), 1 warning(s) C:\wix3-sources\wix.build(120,6): Building WiX requires the Windows Server 2008 and .NET Framework 3.5 SDK or Visual Studio 2008 Total time: 0.7 seconds. C:\wix3-sources Christopher Painter, MCSE, Author of: Deployment Engineering Blog Factory Provider for ADO.NET 2.0 (Work In Progress) Bottles Of Beer - Windows Installer - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Localizing properties in WiX 2.0
Thanks Jim, that's exactly what I was looking for :) Alex G. -- Property Id=PREVENT_DOWNGRADE$(loc.PREVENT_DOWNGRADE)/Property Note, you would then also need an English translation .wxl file as well for English strings. Jim - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005
It's been so long since I've looked at Votive 2.0, but I seem to remember that it doesn't support it. Just a note that Votive 2.0 was more of a preview release and we disbanded support for it when we moved to Votive 3.0. Before Christopher Painter jumps in and tells us that this is a bad customer solution J, I'll freely admit it. However, with the limited amount of developers (at the time it was just me), we decided it was best to put my efforts into making Votive 3.0 include new features than to flesh out and support Votive 2.0. That's a long-winded answer to your question. J Justin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Andersen Sent: Friday, April 25, 2008 8:32 AM To: Jon Andersen; Mark Line; Willie Burton Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 Can a Votive expert help me with this? At the moment, it appears that Votive does not support the UI extension WixUI_InstallDir, but I would be happy to be proven wrong. I am using 2.0. I need to include a localization XML file for WixUI_InstallDir, but I can find no way to accomplish this entirely within Visual Studio. Is there some way to change the light.exe command-line flags WITHIN Visual Studio or the various XML files involved? Does the Votive installation include these XML files or do I ALSO need to install Wix separately? I need to add: -loc C:\Program Files\wix-2.0.5805\WixUI_en-us.wxl or the equivalent within Visual Studio. I don't want to have a parallel build system outside Visual Studio. -Jon Andersen Guardian Team: Securing CPS Citrix Systems, Inc (954) 940-7737 or x27737 This email was sent using RTST Outlook. From: Jon Andersen Sent: Thursday, April 24, 2008 4:15 PM To: 'Mark Line'; 'Willie Burton' Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 Is there some way to tie in the localization XML file using the Visual Studio plug in? I haven't been using makefiles, etc. -Jon Andersen Guardian Team: Securing CPS Citrix Systems, Inc (954) 940-7737 or x27737 This email was sent using RTST Outlook. From: Mark Line [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 2:44 PM To: Jon Andersen; 'Willie Burton' Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 Your need something like this: light -nologo -out myMSI.msi sca.wixlib, wixca.wixlib, and WixUI.wixlib C:\Program Files\wix-2.0.5805\wixui.wixlib -loc C:\Program Files\wix-2.0.5805\WixUI_en-us.wxl From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Andersen Sent: 24 April 2008 07:40 PM To: Willie Burton Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 I'm using Wix 2.0. Currently my references listed are sca.wixlib, wixca.wixlib, and WixUI.wixlib. -Jon From: Willie Burton [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 2:37 PM To: Jon Andersen Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 Did you add the WixUIExtension.dll reference? _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Andersen Sent: Thursday, April 24, 2008 2:33 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using WixUI_InstallDir with Visual Studio 2005 I'm trying to use WixUI_InstallDir inside Visual Studio 2005 (with integration installed) and have run into an issue. Apparently the light linker needs to be given a localization XML file, but I can't figure out how to give it to it. The error message is: light.exe : error LHGT0122: The localization string 'WixUIOK' is unknown. Ensure that the localization variable $(loc.WixUIOK) is defined. (followed by many other similar error messages). The tutorial suggests setting the Culture property of the Linker in the project properties; however, I can't find that property. Any suggestions? Thanks, -Jon - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Build Bug?
The 4 registry errors are known and normal. NAnt issues errors when it can't find the registry key even when we have failOnError=false in the NAnt files. If you know of a way to get rid of those non-fatal errors we'd gladly take the fix. I've gotten used to seeing the errors, so I just ignore them. J The warning, however, is something we should fix and is what is causing your build to fail. Justin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Painter Sent: Friday, April 25, 2008 11:49 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX Build Bug? I've downloaded the latest WiX source package. I've got Visual Studio 2008 Pro from MSDN ( SW_DVD9_Visual_Studio_Pro_2008_English_Core_MLF_X14-26326.ISO ) and the latest Server 2008 PSDK installed aswell as the latest beta NAnt build. I try to run make.bat and I get the following error. When I look in the registry I have a Setup key with 12 subkeys... none of which are the ones the build script is looking for. C:\wix3-sourcesmake NAnt 0.86 (Build 0.86.2962.0; nightly; 2/10/2008) Copyright (C) 2001-2008 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///C:/wix3-sources/wix.build file:///C:\wix3-sources\wix.build Target framework: Microsoft .NET Framework 2.0 Target(s) specified: inc [property] Read-only property dir.src.dutil cannot be overwritten. [readregistry] Registry Path Not Found! - key='SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VS\VSDB\';hive='Microsoft.Win 32.RegistryHive[]'; [readregistry] Registry Path Not Found! - key='SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VS\VSTD\';hive='Microsoft.Win 32.RegistryHive[]'; [readregistry] Registry Path Not Found! - key='SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VS\VSTS\';hive='Microsoft.Win 32.RegistryHive[]'; [readregistry] Registry Path Not Found! - key='SOFTWARE\Microsoft\VisualStudio\9.0\Setup\VS\VSTT\';hive='Microsoft.Win 32.RegistryHive[]'; [echo] VS Test Tools are installed. The Tests will be built. prereqcheck: BUILD FAILED - 4 non-fatal error(s), 1 warning(s) C:\wix3-sources\wix.build(120,6): Building WiX requires the Windows Server 2008 and .NET Framework 3.5 SDK or Visual Studio 2008 Total time: 0.7 seconds. C:\wix3-sources Christopher Painter, MCSE, Author of: Deployment Engineering Blog http://blog.deploymentengineering.com/ Factory Provider for ADO.NET 2.0 http://www.codeplex.com/MSIProviderI (Work In Progress) Bottles http://99-bottles-of-beer.net/language-windows-installer-1310.html Of Beer - Windows Installer _ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try http://us.rd.yahoo.com/evt=51733/*http:/mobile.yahoo.com/;_ylt=Ahu06i62sR8H DtDypao8Wcj9tAcJ%20 it now. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uncompressed files not showing up in install image
Here is how all this compression/CAB embedding seems to work: To set the compression state of the file use: - Package/@Compressed - this will set the default state for all files in the installation package. - File/@Compressed - overrides the package level setting on per-file basis. What Compressed=no means: It means that file will not be included in the CAB file and has to be distributed along with the msi file. Compressed=yes means that file will be included in the CAB file and File/@DiskId determines which one CAB file it will be. Use Media/@CompressionLevel to set the compression level for files stored in the CAB file. One of the settings is none - means, files will be stored in the CAB file without compression. Use Media/EmbedCab=yes to embed the CAB file into msi file and Media/EmbedCab=no to have it as a standalone file which will be distributed along with msi file. For more detailed explanation see: http://blogs.technet.com/alexshev/archive/2008/04/04/from-msi-to-wix-part-16-installable-items-handling-installation-media.aspx Do you want all files to not be included in the msi or you don't want them to be compressed, but still included in the msi? Alex From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Tsuji Sent: Friday, April 25, 2008 3:22 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Uncompressed files not showing up in install image I'm having a problem building a WiX project in which I'm trying to specify all of my files as uncompressed. Currently I do have a working project with the files compressed into the MSI, but I need to change this to make them uncompressed on the install image. What I've tried so far is to change the Compressed=yes attribute to Compressed=no on all the File elements, and remove the Cabinet and EmbedCab attributes in the Media element. The WiX project then builds without errors, but the resulting image does not contain my files, and launching the MSI produces an error that it can't find the files at their specified location. What can cause this to happen? Here is an example of the Directory, Feature, and Media elements in my wxs file. (File and directory names have been changed for security purposes, and I've only listed one file, though my actual wxs contains many files that follow the same format.) Directory Id=ProgramFilesFolder SourceName=PROGRA~1 LongSource=program files Directory Id=MY_PRODUCT_NAME Name=MYPROD~1 LongName=My Product Name Directory Id=INSTALLDIR src=MySourceFolder Component Id=MyComponentName Guid=3513EC11-E682-406C-84DF-D2407619AD40 SharedDllRefCount=yes File Id=My.File.Name Name=MY19A4~1.DLL LongName=My.File.Name.dll Compressed=no KeyPath=yes DiskId=1 / /Component /Directory /Directory /Directory Feature Id=Application_Files Title=Application Files Level=1 ConfigurableDirectory=INSTALLDIR ComponentRef Id=MyComponentName / /Feature Media Id=1 DiskPrompt=1 VolumeLabel=DISK1 / Let me know if I need to provide more details. Thanks. Wayne Tsuji Software Design Engineer Microsoft Dynamics Point of Sale - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
