Re: [WiX-users] Wix Burn: Bundle condition does not work if using MBA
The WixBA at src\Setup\WixBA is the C# managed BA that is used by the installer that installs the toolset. The Bundle does not have a bal:Condition in it and as far as I can tell there is nothing directly related to Bal:Condition in WixBA. However I think what folks have suggested is that one could look at how the processing of bal:Condition is implemented in the C++ WixStdBA at src\ext\BalExtensions\wixstdba and using that functionality as a pattern implement something like that in the managed BA that you are writing. I think one would want to look at EvaluateConditions in WixStandardBootstrapperApplication.cpp for a starter. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-Bundle-condition-does-not-work-if-using-MBA-tp7581757p758.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need to help! Uninstall the MSI on windows 7
Blair, sorry to bother you. I ran the log file on windows xp and got same
results and 'Assets' folder got removed. So why not on win 7?
Thanks,
Balu
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Thursday, August 01, 2013 10:39 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Need to help! Uninstall the MSI on windows 7
Not all components were removed, so the removal wasn't complete. It appears
that the Assets folder only has subfolders and not files directly in it, so
without all components being removed it may have skipped removing all folders
in case they were still needed.
MSI (s) (2C:D0) [08:49:30:611]: Component: MainDesktopShortcutComponent;
Installed: Local; Request: Absent; Action: Null
MSI (s) (2C:D0) [08:49:30:611]: Component: MainStartmenuComponent; Installed:
Local; Request: Absent; Action: Null
Is there another product that shares the component GUIDs of those two
components installed?
From: balu.mam...@flightsafety.com
To: wix-users@lists.sourceforge.net
CC: os...@live.com
Date: Thu, 1 Aug 2013 10:04:57 -0400
Subject: RE: [WiX-users] Need to help! Uninstall the MSI on windows 7
Yes I did create the log file( see the attached file)
This file created on windows 7, it says Removal completed
successfully, but leaving ASSETS empty folder (again this issue only
on windows 7, on windows xp loks good)
Thanks
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Wednesday, July 31, 2013 5:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need to help! Uninstall the MSI on windows 7
Did you create a verbose log when you ran the uninstall? What did that log
say? Did you see my reply on this thread where I asked about the log?
From: balu.mam...@flightsafety.com
To: wix-users@lists.sourceforge.net
Date: Wed, 31 Jul 2013 17:26:28 -0400
Subject: Re: [WiX-users] Need to help! Uninstall the MSI on windows
7
Any other suggestions? This is last bug to send to LIVE..
-Original Message-
From: Mamidi, Balasubrahmanyam
Sent: Wednesday, July 31, 2013 12:33 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Need to help! Uninstall the MSI on windows
7
Yes folder exists after rebooted.
Thanks..
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Wednesday, July 31, 2013 11:58 AM
To: General discussion for Windows Installer XML toolset.
Cc: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need to help! Uninstall the MSI on windows
7
Is the folder there after a reboot?
Sent from my iPhone
On Jul 31, 2013, at 11:16 AM, Blair Murri os...@live.com wrote:
What does the log say?
Most often it is that a file was held by something (usually anti-virus)
but released before the transaction finished (the file was thus deleted
by the time everything finished).
Is it very reproducible?
From: balu.mam...@flightsafety.com
To: wix-users@lists.sourceforge.net
Date: Wed, 31 Jul 2013 11:04:01 -0500
Subject: [WiX-users] Need to help! Uninstall the MSI on windows
7
HI, when uninstall the msi package no issues on windowsXP( it
deletes all folders/subfolders/files etc..)
When I do the same thing on Wndows 7 , it just left ONE sub
folder, but deletes all files with in that...(can say EMPTY
folder)
Any guess what is causing for NOT DELETING THAT SUB FOLDER?
Thanks,
Balu
-
--
--
- Get your SQL database under version control now!
Version control is standard for application code, but databases
havent caught up. So what steps can you take to put your SQL
databases under version control? Why should you start doing it? Read
more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.
clktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
--
--
Get your SQL database under version control now!
Version control is standard for application code, but databases
havent caught up. So what steps can you take to put your SQL
databases under version control? Why should you start doing it? Read more
to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/os
tg .c lktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Get
Re: [WiX-users] multi-language bundle - A BIG THANKS
Hi Phil, Glad to help, and thanks for the suggestions. It does make sense to localize the theme itself, though I have not done so yet. Did you try it? Alnoor -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587780.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] multi-language bundle - A BIG THANKS
My experiments so far do not work. I added: Payload Id=themeXml_de_de Compressed=yes Name=1031\HyperlinkTheme.xml SourceFile=theme\1031\HyperlinkTheme.xml/ And made various changes to only that xml file, but so far it has not picked it up. I was just starting to read through the source code, but do not have anything figured out yet. Anyway the big issue was getting the translated strings int the dialog. For some reason though, some languages don't have enough space to say what needs to be said. :( Not a big deal, we can make it work. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587781.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] 400MB Patch taking more than 40 minutes to execute. Is that normal ?!
We have the following scenario: - base installation with 14k files, 800MB msi file and about 1,4GB after installation - patch changing about 2k files and adding 13k files, 400MB msp file - base installation took about 5-7 minutes to install - patch took more than 40 minutes to apply (msiexec running at an average CPU load of 80%) Only about 10MB per minute isn't normal, is it? (Using a major upgrade rather than a patch might be faster here, but the main goal right now is evaluating WiX's (and Windows installer's) patch performance.) 1. Is Windows Installer running a lot of tests while executing a patch rather than just applying the necessary changes? 2. Is Windows Installer known to perform badly when the installation has more than 20k files? 3. Are RemoveFile operations slowing down patch execution? 4. Is WiX patch generation slowed stronger by number of files or size of files to compare? 5. Does Windows Installer generally have a lousy performance when it comes to patching? 6. Are there things known to slow down patching ? (apart from very many or very large files :P) Any shared experience would be much appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/400MB-Patch-taking-more-than-40-minutes-to-execute-Is-that-normal-tp7587782.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] multi-language bundle - A BIG THANKS
It looks like the answer to loading a localized xml file is here: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localized-bundle-Picking-up-the-right-files-td7265208.html I have not tried it yet, but he is correct that I did not have the png file in each localized folder. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587783.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding event source during install
The goal is to set the installation directory to C:\Program Files\Ent Federal Credit Union\ProductName This produces a build error: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Name=ProgramFiles Directory Id=Manufacturer Name=Company Directory Id=INSTALLLOCATION Name=LogonTimerService/Directory /Directory /Directory /Directory Error 2 ICE99: The directory name: Manufacturer is the same as one of the MSI Public Properties and can cause unforeseen side effects. I found somewhere that using a custom action I could set a directory value using the [Manufacturer] property. Is there another way? Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 4:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install Why are you setting TARGETDIR with a custom action?This is not usually a good practice, and overriding TARGETDIR is usually reserved for activities like admin installs. If you want to set up a variable InstallLocation, there are much better patterns to follow to achieve this. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 5:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install From the log file it seems my custom action that sets the TARGETDIR is the thing throwing the error: Action 16:03:18: SetTARGETDIR. Action start 16:03:18: SetTARGETDIR. MSI (c) (58:18) [16:03:18:241]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\'. Its new value: 'C:\Program Files\Ent Federal Credit Union\'. MSI (c) (58:18) [16:03:18:241]: Note: 1: 1324 2: ? 3: 1 MSI (c) (58:18) [16:03:18:241]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:18:241]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1324 Error 1324. The folder path '?' contains an invalid character. MSI (c) (58:18) [16:03:23:420]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:23:420]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (c) (58:18) [16:03:23:420]: Product: LogonTimerService -- Error 1324. The folder path '?' contains an invalid character. Action ended 16:03:23: SetTARGETDIR. Return value 3. MSI (c) (58:18) [16:03:23:422]: Doing action: FatalError CustomAction Id=SetTARGETDIR Directory=TARGETDIR Value=[ProgramFiles64Folder][Manufacturer] Return=check / InstallUISequence Custom Action=SetTARGETDIR After=CostFinalize / /InstallUISequence So then the question is. Why does adding the EventSource node cause the custom action to fail? I'm going to get another log with the EventSource removed and see what is different. Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 3:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install So, what does NETFRAMEWORK20INSTALLROOTDIR64 evaluate to from the install log? -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 4:37 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] adding event source during install I would like to add this node to my component, to make sure a specific event source exists: util:EventSource Log=Application Name=LogonTimer EventMessageFile=[NETFRAMEWORK20INSTALLROOTDIR64]EventLogMessages.dll / I have these also: PropertyRef Id=NETFRAMEWORK20 / PropertyRef Id=NETFRAMEWORK20INSTALLROOTDIR64 / PropertyRef Id=NETFRAMEWORK40FULL / PropertyRef Id=NETFRAMEWORK40FULLINSTALLROOTDIR64 / Just in case adding more of them would make the problem go away. And this: xmlns:util=https://urldefense.proofpoint.com/v1/url?u=http://schemas.microsoft.com/wix/UtilExtensionk=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0Ar=YFkUslLBsKTVopesyo1A5w%3D%3D%0Am=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0As=d4af28933ca92a0227b24ff2b3b8cfc56b3211014a888e74f31ef5f020c14fc4; The project builds, but as soon as the msi runs it throws an error The folder path '?' has an invalid character (well duh, ? is invalid) If I comment this EventSource node out, the installer runs just fine. I have
Re: [WiX-users] Need to help! Uninstall the MSI on windows 7
MSI's code is different between different platforms. You could file a bug with Microsoft. Sometimes adding a CreateFolder or RemoveFolder fixes these things. Try the CreateFolder first. From: balu.mam...@flightsafety.com To: wix-users@lists.sourceforge.net Date: Fri, 2 Aug 2013 10:15:44 -0400 Subject: Re: [WiX-users] Need to help! Uninstall the MSI on windows 7 Blair, sorry to bother you. I ran the log file on windows xp and got same results and 'Assets' folder got removed. So why not on win 7? Thanks, Balu -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: Thursday, August 01, 2013 10:39 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Need to help! Uninstall the MSI on windows 7 Not all components were removed, so the removal wasn't complete. It appears that the Assets folder only has subfolders and not files directly in it, so without all components being removed it may have skipped removing all folders in case they were still needed. MSI (s) (2C:D0) [08:49:30:611]: Component: MainDesktopShortcutComponent; Installed: Local; Request: Absent; Action: Null MSI (s) (2C:D0) [08:49:30:611]: Component: MainStartmenuComponent; Installed: Local; Request: Absent; Action: Null Is there another product that shares the component GUIDs of those two components installed? From: balu.mam...@flightsafety.com To: wix-users@lists.sourceforge.net CC: os...@live.com Date: Thu, 1 Aug 2013 10:04:57 -0400 Subject: RE: [WiX-users] Need to help! Uninstall the MSI on windows 7 Yes I did create the log file( see the attached file) This file created on windows 7, it says Removal completed successfully, but leaving ASSETS empty folder (again this issue only on windows 7, on windows xp loks good) Thanks -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: Wednesday, July 31, 2013 5:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need to help! Uninstall the MSI on windows 7 Did you create a verbose log when you ran the uninstall? What did that log say? Did you see my reply on this thread where I asked about the log? From: balu.mam...@flightsafety.com To: wix-users@lists.sourceforge.net Date: Wed, 31 Jul 2013 17:26:28 -0400 Subject: Re: [WiX-users] Need to help! Uninstall the MSI on windows 7 Any other suggestions? This is last bug to send to LIVE.. -Original Message- From: Mamidi, Balasubrahmanyam Sent: Wednesday, July 31, 2013 12:33 PM To: 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Need to help! Uninstall the MSI on windows 7 Yes folder exists after rebooted. Thanks.. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, July 31, 2013 11:58 AM To: General discussion for Windows Installer XML toolset. Cc: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need to help! Uninstall the MSI on windows 7 Is the folder there after a reboot? Sent from my iPhone On Jul 31, 2013, at 11:16 AM, Blair Murri os...@live.com wrote: What does the log say? Most often it is that a file was held by something (usually anti-virus) but released before the transaction finished (the file was thus deleted by the time everything finished). Is it very reproducible? From: balu.mam...@flightsafety.com To: wix-users@lists.sourceforge.net Date: Wed, 31 Jul 2013 11:04:01 -0500 Subject: [WiX-users] Need to help! Uninstall the MSI on windows 7 HI, when uninstall the msi package no issues on windowsXP( it deletes all folders/subfolders/files etc..) When I do the same thing on Wndows 7 , it just left ONE sub folder, but deletes all files with in that...(can say EMPTY folder) Any guess what is causing for NOT DELETING THAT SUB FOLDER? Thanks, Balu - -- -- - Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg. clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- -- -- Get your SQL database under version control now! Version control is standard for application code, but databases
Re: [WiX-users] adding event source during install
Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Name=ProgramFiles Directory Id=Us Name=Company Directory Id=INSTALLLOCATION Name=LogonTimerService/Directory /Directory /Directory /Directory Directory Ids are always MSI session Properties, so don't allow them to conflict. From: twh...@ent.com To: wix-users@lists.sourceforge.net Date: Fri, 2 Aug 2013 17:07:53 + Subject: Re: [WiX-users] adding event source during install The goal is to set the installation directory to C:\Program Files\Ent Federal Credit Union\ProductName This produces a build error: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Name=ProgramFiles Directory Id=Manufacturer Name=Company Directory Id=INSTALLLOCATION Name=LogonTimerService/Directory /Directory /Directory /Directory Error 2 ICE99: The directory name: Manufacturer is the same as one of the MSI Public Properties and can cause unforeseen side effects. I found somewhere that using a custom action I could set a directory value using the [Manufacturer] property. Is there another way? Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 4:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install Why are you setting TARGETDIR with a custom action?This is not usually a good practice, and overriding TARGETDIR is usually reserved for activities like admin installs. If you want to set up a variable InstallLocation, there are much better patterns to follow to achieve this. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 5:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install From the log file it seems my custom action that sets the TARGETDIR is the thing throwing the error: Action 16:03:18: SetTARGETDIR. Action start 16:03:18: SetTARGETDIR. MSI (c) (58:18) [16:03:18:241]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\'. Its new value: 'C:\Program Files\Ent Federal Credit Union\'. MSI (c) (58:18) [16:03:18:241]: Note: 1: 1324 2: ? 3: 1 MSI (c) (58:18) [16:03:18:241]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:18:241]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1324 Error 1324. The folder path '?' contains an invalid character. MSI (c) (58:18) [16:03:23:420]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:23:420]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (c) (58:18) [16:03:23:420]: Product: LogonTimerService -- Error 1324. The folder path '?' contains an invalid character. Action ended 16:03:23: SetTARGETDIR. Return value 3. MSI (c) (58:18) [16:03:23:422]: Doing action: FatalError CustomAction Id=SetTARGETDIR Directory=TARGETDIR Value=[ProgramFiles64Folder][Manufacturer] Return=check / InstallUISequence Custom Action=SetTARGETDIR After=CostFinalize / /InstallUISequence So then the question is. Why does adding the EventSource node cause the custom action to fail? I'm going to get another log with the EventSource removed and see what is different. Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 3:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install So, what does NETFRAMEWORK20INSTALLROOTDIR64 evaluate to from the install log? -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 4:37 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] adding event source during install I would like to add this node to my component, to make sure a specific event source exists: util:EventSource Log=Application Name=LogonTimer EventMessageFile=[NETFRAMEWORK20INSTALLROOTDIR64]EventLogMessages.dll / I have these also: PropertyRef Id=NETFRAMEWORK20 / PropertyRef Id=NETFRAMEWORK20INSTALLROOTDIR64 / PropertyRef Id=NETFRAMEWORK40FULL / PropertyRef
Re: [WiX-users] adding event source during install
It means what it says. There's already a Manufacturer property. I use the Directory@Id CompanyFolder. Rather than go through all the machinations, use WixUI_InstallDir and let it adjust your INSTALLLOCATION. There's documentation on this in both the WiX help and the on-line tutorials. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Friday, August 02, 2013 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install The goal is to set the installation directory to C:\Program Files\Ent Federal Credit Union\ProductName This produces a build error: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Name=ProgramFiles Directory Id=Manufacturer Name=Company Directory Id=INSTALLLOCATION Name=LogonTimerService/Directory /Directory /Directory /Directory Error 2 ICE99: The directory name: Manufacturer is the same as one of the MSI Public Properties and can cause unforeseen side effects. I found somewhere that using a custom action I could set a directory value using the [Manufacturer] property. Is there another way? Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 4:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install Why are you setting TARGETDIR with a custom action?This is not usually a good practice, and overriding TARGETDIR is usually reserved for activities like admin installs. If you want to set up a variable InstallLocation, there are much better patterns to follow to achieve this. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 5:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install From the log file it seems my custom action that sets the TARGETDIR is the thing throwing the error: Action 16:03:18: SetTARGETDIR. Action start 16:03:18: SetTARGETDIR. MSI (c) (58:18) [16:03:18:241]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\'. Its new value: 'C:\Program Files\Ent Federal Credit Union\'. MSI (c) (58:18) [16:03:18:241]: Note: 1: 1324 2: ? 3: 1 MSI (c) (58:18) [16:03:18:241]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:18:241]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1324 Error 1324. The folder path '?' contains an invalid character. MSI (c) (58:18) [16:03:23:420]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:23:420]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (c) (58:18) [16:03:23:420]: Product: LogonTimerService -- Error 1324. The folder path '?' contains an invalid character. Action ended 16:03:23: SetTARGETDIR. Return value 3. MSI (c) (58:18) [16:03:23:422]: Doing action: FatalError CustomAction Id=SetTARGETDIR Directory=TARGETDIR Value=[ProgramFiles64Folder][Manufacturer] Return=check / InstallUISequence Custom Action=SetTARGETDIR After=CostFinalize / /InstallUISequence So then the question is. Why does adding the EventSource node cause the custom action to fail? I'm going to get another log with the EventSource removed and see what is different. Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 3:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install So, what does NETFRAMEWORK20INSTALLROOTDIR64 evaluate to from the install log? -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 4:37 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] adding event source during install I would like to add this node to my component, to make sure a specific event source exists: util:EventSource Log=Application Name=LogonTimer EventMessageFile=[NETFRAMEWORK20INSTALLROOTDIR64]EventLogMessages.dll / I have these also: PropertyRef Id=NETFRAMEWORK20 / PropertyRef
Re: [WiX-users] Replace a file in MSI
If it's a data file the MsiFileHash table may need an update. MsiFiler.exe from the Windows SDK might be useful. Phil -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: Thursday, August 01, 2013 6:57 AM To: chr...@iswix.com; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Replace a file in MSI Hi Christopher, That certainly seems a far better approach. Would you have an example or point me in thr right direction on how to implement this please? Thank You Natalie Carr -Original Message- From: Christopher Painter [mailto:chr...@iswix.com] Sent: 01 August 2013 14:48 To: General discussion for Windows Installer XML toolset.; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Replace a file in MSI I take a slightly different approach. Not as optimal but simpler and less invasive. Using C#/DTF: Create a new cab with my file. Stream cab into MSI Update Media Table Update File Table This essentially orphans the original file and touches as little MSI table data as possible. From: Natalie Carr natalie.c...@measuresoft.com Sent: Thursday, August 01, 2013 8:41 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Replace a file in MSI Hi everyone, I have a customer who would like to replace a certain file in my MSI setup. At the moment I am currently writing a guide on how to do this and at the moment I have this scenario: Remove cab from MSI Extract all files from Cab Replace file Rebuild cab file Add cab back into MSI This is done using the SDK commands. Is there an easier way to do this via orca/transforms? My user wold like the new file embedded inside the MSI and not at the root folder. Thank you. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding event source during install
If the problem is actually related to the event log source, then back to John's question: What does NETFRAMEWORK20INSTALLROOTDIR64 evaluate to? The log fragment you show isn't obviously anything to do with the event log - it seems to related to TARGETDIR and Windows perhaps trying to resolve folder values correctly. I've seen this when shell folder values in the registry are wrong. There are several versions of these in the registry per machine, per user and shell folders/user shell folders as well as native and Wow6432. You may have done something that resolves to a folder that Windows needs to verify for something like WIN64DUALFOLDERS and something is wrong in the registry. Ok, found a somewhat old kb article: http://support.microsoft.com/kb/292582 Phil -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 3:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install Why are you setting TARGETDIR with a custom action?This is not usually a good practice, and overriding TARGETDIR is usually reserved for activities like admin installs. If you want to set up a variable InstallLocation, there are much better patterns to follow to achieve this. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 5:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install From the log file it seems my custom action that sets the TARGETDIR is the thing throwing the error: Action 16:03:18: SetTARGETDIR. Action start 16:03:18: SetTARGETDIR. MSI (c) (58:18) [16:03:18:241]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\'. Its new value: 'C:\Program Files\Ent Federal Credit Union\'. MSI (c) (58:18) [16:03:18:241]: Note: 1: 1324 2: ? 3: 1 MSI (c) (58:18) [16:03:18:241]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:18:241]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1324 Error 1324. The folder path '?' contains an invalid character. MSI (c) (58:18) [16:03:23:420]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:23:420]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (c) (58:18) [16:03:23:420]: Product: LogonTimerService -- Error 1324. The folder path '?' contains an invalid character. Action ended 16:03:23: SetTARGETDIR. Return value 3. MSI (c) (58:18) [16:03:23:422]: Doing action: FatalError CustomAction Id=SetTARGETDIR Directory=TARGETDIR Value=[ProgramFiles64Folder][Manufacturer] Return=check / InstallUISequence Custom Action=SetTARGETDIR After=CostFinalize / /InstallUISequence So then the question is. Why does adding the EventSource node cause the custom action to fail? I'm going to get another log with the EventSource removed and see what is different. Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 3:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install So, what does NETFRAMEWORK20INSTALLROOTDIR64 evaluate to from the install log? -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 4:37 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] adding event source during install I would like to add this node to my component, to make sure a specific event source exists: util:EventSource Log=Application Name=LogonTimer EventMessageFile=[NETFRAMEWORK20INSTALLROOTDIR64]EventLogMessages.dll / I have these also: PropertyRef Id=NETFRAMEWORK20 / PropertyRef Id=NETFRAMEWORK20INSTALLROOTDIR64 / PropertyRef Id=NETFRAMEWORK40FULL / PropertyRef Id=NETFRAMEWORK40FULLINSTALLROOTDIR64 / Just in case adding more of them would make the problem go away. And this: xmlns:util=https://urldefense.proofpoint.com/v1/url?u=http://schemas.micros oft.com/wix/UtilExtensionk=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0Ar=YFkUslLBsK TVopesyo1A5w%3D%3D%0Am=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A s=d4af28933ca92a0227b24ff2b3b8cfc56b3211014a888e74f31ef5f020c14fc4 The project builds, but as soon as the msi runs it throws an error The folder path '?' has an invalid character (well duh, ? is invalid) If I comment this EventSource node out, the installer runs just fine. I have tried EventMessageFile=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\EventLogMe
Re: [WiX-users] 400MB Patch taking more than 40 minutes to execute. Is that normal ?!
What does your patch log show as being the places that more time is used? You can compare the install log and patch log to see where the differences in processing are occurring. Unless you have RemoveFile operations that run at install (as opposed to remove) then there shouldn't be any RemoveFile happening. Are you using delta or whole-file patching? When patching, Windows Installer will copy all files to be patched to a cache, and if you are using delta patches it will verify the applicability of the patch to the file being patched, before it actually starts altering the files themselves. Each of those file operations (including the stream and cabinet extractions required to support them) are all run serially on a single thread in the MSI service and depend greatly on both the speed of the disks/filesystem and the memory pressures on the OS's file cache. Remember that applying a patch is a repair operation so any custom actions that run in your repairs will affect your patching as well. If you can limit which features are patched, and you use feature installation to filter your custom actions, you can limit the time spent on unneeded activities. If you have just one feature, you are reinstalling all 27k files, not just the 15k you are changing/adding. Also Windows Installer does slow down once certain limits of number of components are reached. How many seems to depend somewhat on the platforms involved and their configurations, I haven't seen hard numbers. By comparison your major upgrade still has to evaluate the installation would be upgrading, so I wouldn't be surprised to see it slightly more than double the time compared to the original clean install (you appear to have almost doubled your install size with this patch). Date: Fri, 2 Aug 2013 09:35:17 -0700 From: philipp.ew...@asamnet.de To: wix-users@lists.sourceforge.net Subject: [WiX-users] 400MB Patch taking more than 40 minutes to execute. Is that normal ?! We have the following scenario: - base installation with 14k files, 800MB msi file and about 1,4GB after installation - patch changing about 2k files and adding 13k files, 400MB msp file - base installation took about 5-7 minutes to install - patch took more than 40 minutes to apply (msiexec running at an average CPU load of 80%) Only about 10MB per minute isn't normal, is it? (Using a major upgrade rather than a patch might be faster here, but the main goal right now is evaluating WiX's (and Windows installer's) patch performance.) 1. Is Windows Installer running a lot of tests while executing a patch rather than just applying the necessary changes? 2. Is Windows Installer known to perform badly when the installation has more than 20k files? 3. Are RemoveFile operations slowing down patch execution? 4. Is WiX patch generation slowed stronger by number of files or size of files to compare? 5. Does Windows Installer generally have a lousy performance when it comes to patching? 6. Are there things known to slow down patching ? (apart from very many or very large files :P) Any shared experience would be much appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/400MB-Patch-taking-more-than-40-minutes-to-execute-Is-that-normal-tp7587782.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error
The error message should be different. Please file a bug. Date: Thu, 1 Aug 2013 08:34:52 -0700 From: phogl...@rimage.com To: wix-users@lists.sourceforge.net Subject: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error VS2010/Votive displays bal:Overridable as an attribute option for Bundle/Chain/MsiPackage. While I did not find this attribute documented in the Schema for MsiPackage (as it is for the Variable element) I wondered if I could set it and then (just guessing) pass a property on the command line to my WixStdBA and see if that property got added to this MsiPackage's property list or the msi's command line. (I am aware the I can define a Variable with bal:Overridable and use the variable to set a MsiProperty, but I wondered why the bal:Overridable was offered as an attribute to MsiPackage.) When MsiPackage/@bal:Overridable=yes if provided the following compile error is observed: C:\Program Files (x86)\WiX Toolset v3.7\bin\candle.exe -dDebug -dDEBUG -dDevEnvDir=c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\\ -dSolutionDir=project path\ -dSolutionExt=.sln -...wix tools\WiX Toolset v3.7\bin\\WixBalExtension.dll file1.wxs file2.wxs file3.wxs file4.wxs file5.wxs Windows Installer Xml Compiler version 3.7.1224.0 Copyright (C) Outercurve Foundation. All rights reserved. file1.wxs file2.wxs file3.wxs path to file3.wxs(76,0): error CNDL0005: The MsiPackage element contains an unexpected child element 'MsiPackage'. file4.wxs file5.wxs Done building project QDsetup.wixproj -- FAILED. When I remove the MsiPackage/@bal:Overidable=yes then the project compiles and runs as expected. So I will leave this experiment alone and implement a Variable/@bal:Overidable to address my need pass a property to the msi package. But I wondered if this error message made sense to anyone? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-MsiPackge-bal-Overridable-yes-yeilds-strange-error-tp7587767.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] multi-language bundle - A BIG THANKS
Cool, thanks. If worst comes to worst, I'll just fire up Process Monitor again and watch the file system activity to see what files the bootstrapper is looking for (and not finding.) Somehow, that feels more fun than wading through source code. Alnoor -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587794.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error
I'm sorry, I have looked at the bug tracking page (and other tabs) and I don't see how to file the bug. I would like to understand how to do it. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-MsiPackge-bal-Overridable-yes-yeilds-strange-error-tp7587767p7587795.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] multi-language bundle - A BIG THANKS
Well I got it working. As posted earlier I added a modified HyperlinkTheme.xml to my 1031 subfolder, and originally I added this Payload statement: Payload Id=themeXml_de_de Compressed=yes Name=1031\thm.xml SourceFile=theme\1031\HyperlinkTheme.xml/ The bundle project builds but when run it does not display any dialog and the log file shows error creating the main window (as reported in the other thread referenced). The correct solution at that point is to add the logo.png file to the 1031 folder and add: Payload Id=logo_de_de Compressed=yes Name=1031\logo.png SourceFile=theme\1031\logo.png/ Now when -lang 1031 is used the dialog has the changes which were made in the 1031 version of the XML file (and in looking at the source code I did not see anything that would select the language file based on the users/systems default language. Prior to doing the above I took the unnecessary side track of changing the Payload to: Payload Id=themeXml_de_de Compressed=yes Name=1031\HyperlinkTheme.xml SourceFile=theme\1031\HyperlinkTheme.xml/ I can see in the code where it is expecting thm.xml, but I did not read all the way through. What it does in ProcessMon is it tries to load 1031\Thm.xml which did not exist, and then it tries to load 1031\hyperlinkTheme.xml and seems to succeed, but the dialog does not reflect the 1031\HyperlinkTheme.xml. However by using the Name=1031\thn.xml it all works. I might also comment that prior to working with the localization I had set my LogoFile attribute to import a .bmp file, and removed the logo.png file from my project. So if I go back and convert my bmp to a png file named logo.png it might be a simpler scenario since the XML files have the logo.png name in the XML file. So all in all it seems to work and I can get the files translated when we submit other projects for translation. Thanks for the help. Phill -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587796.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding event source during install
I don't really understand your suggestion. I have 18 tabs of google searches open, and reading the WiX help, and looking at the source code for four days now. Finally found this: http://stackoverflow.com/questions/16946701/wix-installer-how-can-i-show-the-value-of-manufacturer-in-the-install-path I'm sure this is not the way to do it, but it does have the redeeming quality of working: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Directory Id=ManufacturerFolder Name=!(bind.property.Manufacturer) Directory Id=INSTALLLOCATION Name=!(bind.property.ProductName)/Directory /Directory /Directory /Directory Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Friday, August 02, 2013 11:22 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install It means what it says. There's already a Manufacturer property. I use the Directory@Id CompanyFolder. Rather than go through all the machinations, use WixUI_InstallDir and let it adjust your INSTALLLOCATION. There's documentation on this in both the WiX help and the on-line tutorials. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Friday, August 02, 2013 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install The goal is to set the installation directory to C:\Program Files\Ent Federal Credit Union\ProductName This produces a build error: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Name=ProgramFiles Directory Id=Manufacturer Name=Company Directory Id=INSTALLLOCATION Name=LogonTimerService/Directory /Directory /Directory /Directory Error 2 ICE99: The directory name: Manufacturer is the same as one of the MSI Public Properties and can cause unforeseen side effects. I found somewhere that using a custom action I could set a directory value using the [Manufacturer] property. Is there another way? Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 4:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install Why are you setting TARGETDIR with a custom action?This is not usually a good practice, and overriding TARGETDIR is usually reserved for activities like admin installs. If you want to set up a variable InstallLocation, there are much better patterns to follow to achieve this. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 5:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install From the log file it seems my custom action that sets the TARGETDIR is the thing throwing the error: Action 16:03:18: SetTARGETDIR. Action start 16:03:18: SetTARGETDIR. MSI (c) (58:18) [16:03:18:241]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\'. Its new value: 'C:\Program Files\Ent Federal Credit Union\'. MSI (c) (58:18) [16:03:18:241]: Note: 1: 1324 2: ? 3: 1 MSI (c) (58:18) [16:03:18:241]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:18:241]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1324 Error 1324. The folder path '?' contains an invalid character. MSI (c) (58:18) [16:03:23:420]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:23:420]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (c) (58:18) [16:03:23:420]: Product: LogonTimerService -- Error 1324. The folder path '?' contains an invalid character. Action ended 16:03:23: SetTARGETDIR. Return value 3. MSI (c) (58:18) [16:03:23:422]: Doing action: FatalError CustomAction Id=SetTARGETDIR Directory=TARGETDIR Value=[ProgramFiles64Folder][Manufacturer] Return=check / InstallUISequence Custom Action=SetTARGETDIR After=CostFinalize / /InstallUISequence So then the question is. Why does adding the EventSource node cause the custom action to fail? I'm going to get another log
[WiX-users] Multiple upgrade codes issue
On Tue, 30 Jul 2013 21:50:54 -0700, Blair Murri wrote: You can use the MajorUpgrade element (use the UpgradeCode you prefer in your Product element) and use just the offending UpgradeCode in the Upgrade element (to find/remove versions using it). Blair, I tried that but end up with two rows for the good code in my Upgrade table. Below is my code - am I doing something wrong or does it just not work? Product Id=$(var.ProductCode) Name=$(var.ProductName) Language=$(var.Language) Version=$(var.ProductVersion) UpgradeCode=$(var.UpgradeCode) Manufacturer=$(var.Manufacturer) Package Id=* InstallerVersion=301 Compressed=yes InstallScope=$(var.InstallScope) Manufacturer=$(var.Manufacturer) Description=$(var.Description) Keywords=$(var.Keywords) Comments=(var.CopyRight) / MajorUpgrade Schedule=afterInstallExecute DowngradeErrorMessage=A newer version of [ProductName] is already installed. / Upgrade Id=$(var.WrongUpgradeCode) / ... -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error
You have to create an account and log in and then you see button to create a bug. IIRC. Wes -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: August-02-13 3:36 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error I'm sorry, I have looked at the bug tracking page (and other tabs) and I don't see how to file the bug. I would like to understand how to do it. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-MsiPackge-bal-Overridable-yes-yeilds-strange-error-tp7587767p7587795.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error
Bug created. Thanks for the help. Someday I hope to help fix the bus. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-MsiPackge-bal-Overridable-yes-yeilds-strange-error-tp7587767p7587800.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding event source during install
I like that way. On Fri, Aug 2, 2013 at 12:51 PM, Tony White twh...@ent.com wrote: I don't really understand your suggestion. I have 18 tabs of google searches open, and reading the WiX help, and looking at the source code for four days now. Finally found this: http://stackoverflow.com/questions/16946701/wix-installer-how-can-i-show-the-value-of-manufacturer-in-the-install-path I'm sure this is not the way to do it, but it does have the redeeming quality of working: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Directory Id=ManufacturerFolder Name=!(bind.property.Manufacturer) Directory Id=INSTALLLOCATION Name=!(bind.property.ProductName)/Directory /Directory /Directory /Directory Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Friday, August 02, 2013 11:22 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install It means what it says. There's already a Manufacturer property. I use the Directory@Id CompanyFolder. Rather than go through all the machinations, use WixUI_InstallDir and let it adjust your INSTALLLOCATION. There's documentation on this in both the WiX help and the on-line tutorials. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Friday, August 02, 2013 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install The goal is to set the installation directory to C:\Program Files\Ent Federal Credit Union\ProductName This produces a build error: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Name=ProgramFiles Directory Id=Manufacturer Name=Company Directory Id=INSTALLLOCATION Name=LogonTimerService/Directory /Directory /Directory /Directory Error 2 ICE99: The directory name: Manufacturer is the same as one of the MSI Public Properties and can cause unforeseen side effects. I found somewhere that using a custom action I could set a directory value using the [Manufacturer] property. Is there another way? Thanks, Tony -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, July 31, 2013 4:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install Why are you setting TARGETDIR with a custom action?This is not usually a good practice, and overriding TARGETDIR is usually reserved for activities like admin installs. If you want to set up a variable InstallLocation, there are much better patterns to follow to achieve this. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: Wednesday, July 31, 2013 5:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] adding event source during install From the log file it seems my custom action that sets the TARGETDIR is the thing throwing the error: Action 16:03:18: SetTARGETDIR. Action start 16:03:18: SetTARGETDIR. MSI (c) (58:18) [16:03:18:241]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\'. Its new value: 'C:\Program Files\Ent Federal Credit Union\'. MSI (c) (58:18) [16:03:18:241]: Note: 1: 1324 2: ? 3: 1 MSI (c) (58:18) [16:03:18:241]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:18:241]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1324 Error 1324. The folder path '?' contains an invalid character. MSI (c) (58:18) [16:03:23:420]: Note: 1: 2205 2: 3: Error MSI (c) (58:18) [16:03:23:420]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (c) (58:18) [16:03:23:420]: Product: LogonTimerService -- Error 1324. The folder path '?' contains an invalid character. Action ended 16:03:23: SetTARGETDIR. Return value 3. MSI (c) (58:18) [16:03:23:422]: Doing action: FatalError CustomAction Id=SetTARGETDIR Directory=TARGETDIR Value=[ProgramFiles64Folder][Manufacturer] Return=check / InstallUISequence Custom Action=SetTARGETDIR
[WiX-users] [Votive/Light] LGHT100 error when more than one localized .wxl
This is related to: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-td7208949.html but I thought it best to start a new thread. Using VS2010 3.7.1224 WixStandardBootstrapperApplication.HyperlinkLicense project, I added the following folder tree to my project: ProjectFolder Resources 1031 1034 1036 etc. Using info in the other thread I copied the HyperlinkTheme.wxl (from the Wix 3.7 src) to each folder and modified each wxl file to have the related LCID and translated some text (to allow testing). I ca build the project if I do not import any HyperlinkTheme.wxl file. But if I add more than two of the .wxl files (such as adding the one existing in the 1031 folder and then adding the one existing in the 1034 folder) which allows me to edit these files in VS2010, then the project will not build with the following errors. vc2010_x86.wxs C:\Program Files (x86)\WiX Toolset v3.7\bin\Light.exe -out ...project\bin\Debug\QDsetup.exe -pdbout ...project\bin\Debug\QDsetup.wixpdb -ext ..\WixExt\bin\Debug\WixExt.dll -ext C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixNetFxExtension.dll -ext C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixUtilExtension.dll -ext C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixTagExtension.dll -ext C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixBalExtension.dll -loc Resources\1031\HyperlinkTheme_de_de.wxl -loc Resources\1034\HyperlinkTheme_es_es.wxl -contentsfile obj\Debug\QDsetup.wixproj.BindContentsFileList.txt -outputsfile obj\Debug\QDsetup.wixproj.BindOutputsFileList.txt -builtoutputsfile obj\Debug\QDsetup.wixproj.BindBuiltOutputsFileList.txt -wixprojectfile ...project\QDsetup.wixproj obj\Debug\cddesigner.wixobj obj\Debug\NetFx35.wixobj obj\Debug\QDsetup.wixobj obj\Debug\vc2008_SP1_17.wixobj obj\Debug\vc2010_x86.wixobj Windows Installer Xml Linker version 3.7.1224.0 Copyright (C) Outercurve Foundation. All rights reserved. light.exe(0,0): error LGHT0100: The localization identifier 'InstallLicenseLinkText' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'OptionsLocationLabel' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'SuccessHeader' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'InstallOptionsButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'FailureCloseButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'ModifyRepairButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'ModifyCloseButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'InstallCloseButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'FailureRestartText' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'InstallAcceptCheckbox' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'HelpText' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'SuccessLaunchButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'FailureHyperlinkLogText' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'OptionsOkButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'InstallInstallButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'FailureRestartButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'ModifyUninstallButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'ProgressLabel' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'ConfirmCancelMessage' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The
Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error
You must log into Sourceforge.net using the account you possibly setup when you added yourself to the wix-users list. Once you are logged in, there is a Create ticket button that shows up between the search box and the View Stats button along the left edge of the main box in the window. Date: Fri, 2 Aug 2013 11:36:16 -0700 From: phogl...@rimage.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error I'm sorry, I have looked at the bug tracking page (and other tabs) and I don't see how to file the bug. I would like to understand how to do it. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-MsiPackge-bal-Overridable-yes-yeilds-strange-error-tp7587767p7587795.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multiple upgrade codes issue
MajorUpgrade places common (usually two) rows into the Upgrade table using the UpgradeCode specified in the Product element. One is used for removing previous product versions and the other row is used for preventing downgrades. The additional Upgrade element needs an UpgradeVersion child element setup to detect and remove your WrongUpgradeCode products. The name of the property you use doesn't matter but should be unique (i.e. not the same as any other property either you or WiX is currently using). WRONGUPGRADECODEPRODUCT would probably work just fine. I would recommend including all versions (which I believe is the default). RTFM Blair From: kpet...@otaksoft.com To: wix-users@lists.sourceforge.net Date: Fri, 2 Aug 2013 12:45:32 -0700 Subject: [WiX-users] Multiple upgrade codes issue On Tue, 30 Jul 2013 21:50:54 -0700, Blair Murri wrote: You can use the MajorUpgrade element (use the UpgradeCode you prefer in your Product element) and use just the offending UpgradeCode in the Upgrade element (to find/remove versions using it). Blair, I tried that but end up with two rows for the good code in my Upgrade table. Below is my code - am I doing something wrong or does it just not work? Product Id=$(var.ProductCode) Name=$(var.ProductName) Language=$(var.Language) Version=$(var.ProductVersion) UpgradeCode=$(var.UpgradeCode) Manufacturer=$(var.Manufacturer) Package Id=* InstallerVersion=301 Compressed=yes InstallScope=$(var.InstallScope) Manufacturer=$(var.Manufacturer) Description=$(var.Description) Keywords=$(var.Keywords) Comments=(var.CopyRight) / MajorUpgrade Schedule=afterInstallExecute DowngradeErrorMessage=A newer version of [ProductName] is already installed. / Upgrade Id=$(var.WrongUpgradeCode) / ... -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error
I saw a prior post and created a Sorceforge account and then created the bug. But it is different from the one I was logged into the forum with. In the future I can use the forum login. Sorry for the confusion. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-MsiPackge-bal-Overridable-yes-yeilds-strange-error-tp7587767p7587805.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [Votive/Light] LGHT100 error when more than one localized .wxl
Make the payload (localized) WXL files of type None (using the property area in the lower right corner of the IDE). Date: Fri, 2 Aug 2013 14:07:15 -0700 From: phogl...@rimage.com To: wix-users@lists.sourceforge.net Subject: [WiX-users] [Votive/Light] LGHT100 error when more than one localized .wxl This is related to: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-td7208949.html but I thought it best to start a new thread. Using VS2010 3.7.1224 WixStandardBootstrapperApplication.HyperlinkLicense project, I added the following folder tree to my project: ProjectFolder Resources 1031 1034 1036 etc. Using info in the other thread I copied the HyperlinkTheme.wxl (from the Wix 3.7 src) to each folder and modified each wxl file to have the related LCID and translated some text (to allow testing). I ca build the project if I do not import any HyperlinkTheme.wxl file. But if I add more than two of the .wxl files (such as adding the one existing in the 1031 folder and then adding the one existing in the 1034 folder) which allows me to edit these files in VS2010, then the project will not build with the following errors. vc2010_x86.wxs C:\Program Files (x86)\WiX Toolset v3.7\bin\Light.exe -out ...project\bin\Debug\QDsetup.exe -pdbout ...project\bin\Debug\QDsetup.wixpdb -ext ..\WixExt\bin\Debug\WixExt.dll -ext C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixNetFxExtension.dll -ext C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixUtilExtension.dll -ext C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixTagExtension.dll -ext C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixBalExtension.dll -loc Resources\1031\HyperlinkTheme_de_de.wxl -loc Resources\1034\HyperlinkTheme_es_es.wxl -contentsfile obj\Debug\QDsetup.wixproj.BindContentsFileList.txt -outputsfile obj\Debug\QDsetup.wixproj.BindOutputsFileList.txt -builtoutputsfile obj\Debug\QDsetup.wixproj.BindBuiltOutputsFileList.txt -wixprojectfile ...project\QDsetup.wixproj obj\Debug\cddesigner.wixobj obj\Debug\NetFx35.wixobj obj\Debug\QDsetup.wixobj obj\Debug\vc2008_SP1_17.wixobj obj\Debug\vc2010_x86.wixobj Windows Installer Xml Linker version 3.7.1224.0 Copyright (C) Outercurve Foundation. All rights reserved. light.exe(0,0): error LGHT0100: The localization identifier 'InstallLicenseLinkText' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'OptionsLocationLabel' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'SuccessHeader' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'InstallOptionsButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'FailureCloseButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'ModifyRepairButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'ModifyCloseButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'InstallCloseButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'FailureRestartText' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'InstallAcceptCheckbox' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'HelpText' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'SuccessLaunchButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'FailureHyperlinkLogText' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'OptionsOkButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'InstallInstallButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'FailureRestartButton' has been duplicated in multiple locations. Please resolve the conflict. light.exe(0,0): error LGHT0100: The localization identifier 'ModifyUninstallButton' has been duplicated in
[WiX-users] Adding Downgrade support to MSI
Hi, I have been trying to add Downgrade support to our MSI. I know Uninstall/Re-install is preferred over this, but this is needed for automated deployments and is specially helpful for our zero-downtime product upgrades across multiple machines. So the requirement is that any version can be installed over any other version which is different. I am using the AllowDowngrades=yes option with MajorUpgrade element i.e.ProductId=* .UpgradeCode=GUID MajorUpgrade Schedule=afterInstallInitialize AllowDowngrades=yes / However, I see a few issues while testing downgrade (say installing v1.9 while 2.0 is already installed) - 1. Our wxs file contains one file per component, however all the components are skipped during the installation of v1.9.2. As a result, Custom action execution fails with this error - The File 'File_' is not marked for installation.MSI (s) (A4:E4) [15:45:47:544]: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753. The arguments are: File_, , I would like to know possible ways to solve this problem.Please note that versions of all our files will change across releases. P.S - I read about using REINSTALLMODE=amus to force reinstallation of all files. I also saw comments saying that this is okay for dev testing and is NOT RECOMMENDED for production systems. Regards,Surya -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding Downgrade support to MSI
Are/will any of the binaries you distribute in this product (or ever intend to distribute) ever [be] distributed by any other product? From: surya6...@hotmail.com To: wix-users@lists.sourceforge.net Date: Sat, 3 Aug 2013 04:39:26 +0530 Subject: [WiX-users] Adding Downgrade support to MSI Hi, I have been trying to add Downgrade support to our MSI. I know Uninstall/Re-install is preferred over this, but this is needed for automated deployments and is specially helpful for our zero-downtime product upgrades across multiple machines. So the requirement is that any version can be installed over any other version which is different. I am using the AllowDowngrades=yes option with MajorUpgrade element i.e.ProductId=* .UpgradeCode=GUID MajorUpgrade Schedule=afterInstallInitialize AllowDowngrades=yes / However, I see a few issues while testing downgrade (say installing v1.9 while 2.0 is already installed) - 1. Our wxs file contains one file per component, however all the components are skipped during the installation of v1.9.2. As a result, Custom action execution fails with this error - The File 'File_' is not marked for installation.MSI (s) (A4:E4) [15:45:47:544]: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753. The arguments are: File_, , I would like to know possible ways to solve this problem.Please note that versions of all our files will change across releases. P.S - I read about using REINSTALLMODE=amus to force reinstallation of all files. I also saw comments saying that this is okay for dev testing and is NOT RECOMMENDED for production systems. Regards,Surya -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding Downgrade support to MSI
No, the binaries are specific to a product only and will never be distributed by any other product. From: os...@live.com To: wix-users@lists.sourceforge.net Date: Fri, 2 Aug 2013 20:05:21 -0700 Subject: Re: [WiX-users] Adding Downgrade support to MSI Are/will any of the binaries you distribute in this product (or ever intend to distribute) ever [be] distributed by any other product? From: surya6...@hotmail.com To: wix-users@lists.sourceforge.net Date: Sat, 3 Aug 2013 04:39:26 +0530 Subject: [WiX-users] Adding Downgrade support to MSI Hi, I have been trying to add Downgrade support to our MSI. I know Uninstall/Re-install is preferred over this, but this is needed for automated deployments and is specially helpful for our zero-downtime product upgrades across multiple machines. So the requirement is that any version can be installed over any other version which is different. I am using the AllowDowngrades=yes option with MajorUpgrade element i.e.ProductId=* .UpgradeCode=GUID MajorUpgrade Schedule=afterInstallInitialize AllowDowngrades=yes / However, I see a few issues while testing downgrade (say installing v1.9 while 2.0 is already installed) - 1. Our wxs file contains one file per component, however all the components are skipped during the installation of v1.9.2. As a result, Custom action execution fails with this error - The File 'File_' is not marked for installation.MSI (s) (A4:E4) [15:45:47:544]: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753. The arguments are: File_, , I would like to know possible ways to solve this problem.Please note that versions of all our files will change across releases. P.S - I read about using REINSTALLMODE=amus to force reinstallation of all files. I also saw comments saying that this is okay for dev testing and is NOT RECOMMENDED for production systems. Regards,Surya -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding Downgrade support to MSI
The primary problem with amus is when it is used with anything shared (e.g. the VC merge modules). A secondary problem exists with large MSIs where it causes repairs (and patches) to take longer to run, or where custom actions that use component states are needlessly rerun in patches and repairs. The point is that you need to be certain of every possible contingency and every single scenario, including knowing what scenarios you must exclude from future versions of your product. From: surya6...@hotmail.com To: wix-users@lists.sourceforge.net Date: Sat, 3 Aug 2013 09:00:17 +0530 Subject: Re: [WiX-users] Adding Downgrade support to MSI No, the binaries are specific to a product only and will never be distributed by any other product. From: os...@live.com To: wix-users@lists.sourceforge.net Date: Fri, 2 Aug 2013 20:05:21 -0700 Subject: Re: [WiX-users] Adding Downgrade support to MSI Are/will any of the binaries you distribute in this product (or ever intend to distribute) ever [be] distributed by any other product? From: surya6...@hotmail.com To: wix-users@lists.sourceforge.net Date: Sat, 3 Aug 2013 04:39:26 +0530 Subject: [WiX-users] Adding Downgrade support to MSI Hi, I have been trying to add Downgrade support to our MSI. I know Uninstall/Re-install is preferred over this, but this is needed for automated deployments and is specially helpful for our zero-downtime product upgrades across multiple machines. So the requirement is that any version can be installed over any other version which is different. I am using the AllowDowngrades=yes option with MajorUpgrade element i.e.ProductId=* .UpgradeCode=GUID MajorUpgrade Schedule=afterInstallInitialize AllowDowngrades=yes / However, I see a few issues while testing downgrade (say installing v1.9 while 2.0 is already installed) - 1. Our wxs file contains one file per component, however all the components are skipped during the installation of v1.9.2. As a result, Custom action execution fails with this error - The File 'File_' is not marked for installation.MSI (s) (A4:E4) [15:45:47:544]: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753. The arguments are: File_, , I would like to know possible ways to solve this problem.Please note that versions of all our files will change across releases. P.S - I read about using REINSTALLMODE=amus to force reinstallation of all files. I also saw comments saying that this is okay for dev testing and is NOT RECOMMENDED for production systems. Regards,Surya -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why
