[WiX-users] Wix 3.8 recognized as virus
Hey all - I've been having some problems installing wix 3.8 with avast running - it seems to believe that wix 3.8 is a virus, and that installers generated using it are too. It's reporting my builds as Win32:MalOb-CA now. Anyone else having this problem? -- 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=49501711&iu=/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
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 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: I have these also: 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/UtilExtension&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=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\EventLogMessages.dll", but even that gives the same message. I've googled until my googler is sore, can't discover what is wrong. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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. https://urldefense.proofpoint.com/v1/url?u=http://pubads.g.doubleclick.net/gampad/clk?id%3D49501711%26iu%3D/4140/ostg.clktrk&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=f2bd5c86266ab7f684db698e1f8f0767e577f26c8611423aefea801191142b53 ___ WiX-u
Re: [WiX-users] adding event source during install
With the EventSource node removed: Action 16:25:34: SetTARGETDIR. Action start 16:25:34: SetTARGETDIR. MSI (c) (94:34) [16:25:34:197]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\'. Its new value: 'C:\Program Files\Ent Federal Credit Union\'. MSI (c) (94:34) [16:25:34:197]: PROPERTY CHANGE: Modifying INSTALLLOCATION property. Its current value is 'C:\LogonTimerService\'. Its new value: 'C:\Program Files\Ent Federal Credit Union\LogonTimerService\'. Action ended 16:25:34: SetTARGETDIR. Return value 1. More confused now. -Original Message- From: Tony White Sent: Wednesday, July 31, 2013 4:24 PM To: General discussion for Windows Installer XML toolset. Subject: RE: 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 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: I have these also: 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/UtilExtension&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=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\EventLogMessages.dll", but even that gives the same message. I've googled until my googler is sore, can't discover what is wrong. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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. https://urldefense.proofpoint.com/v1/url?u=http://pubads.g.doubleclick.net/gampad/clk?id%3D49501711%26iu%3D/4140/ostg.clktrk&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=f2bd5c86266ab7f684db698e1f8f0767e577f26c8611423aefea801191142b53
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 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: I have these also: 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/UtilExtension&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=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\EventLogMessages.dll", but even that gives the same message. I've googled until my googler is sore, can't discover what is wrong. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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. https://urldefense.proofpoint.com/v1/url?u=http://pubads.g.doubleclick.net/gampad/clk?id%3D49501711%26iu%3D/4140/ostg.clktrk&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=f2bd5c86266ab7f684db698e1f8f0767e577f26c8611423aefea801191142b53 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://urldefense.proofpoint.com/v1/url?u=https://lists.sourceforge.net/lists/listinfo/wix-users&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=68218b7001788b0269a748059c466cd9ab04496b64651e1d91cc0453416bff08 NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If yo
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" 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=49501711&iu=/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=49501711&iu=/4140/ostg.c > > lktrk ___ > > 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=49501711&iu=/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=49501711&iu=/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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.so
Re: [WiX-users] adding event source during install
Thanks for that, I am just learning WiX and did not know how to make a log file, but now I do. AppSearch: Property: NETFRAMEWORK20INSTALLROOTDIR64, Signature: NetFx20InstallRootSearch64 MSI (c) (58:18) [16:03:18:222]: Note: 1: 2262 2: Signature 3: -2147287038 MSI (c) (58:18) [16:03:18:222]: Note: 1: 1325 2: v2.0.50727 MSI (c) (58:18) [16:03:18:223]: PROPERTY CHANGE: Adding NETFRAMEWORK20INSTALLROOTDIR64 property. Its value is 'C:\Windows\Microsoft.NET\Framework64\v2.0.50727\'. -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: I have these also: 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/UtilExtension&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=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\EventLogMessages.dll", but even that gives the same message. I've googled until my googler is sore, can't discover what is wrong. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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. https://urldefense.proofpoint.com/v1/url?u=http://pubads.g.doubleclick.net/gampad/clk?id%3D49501711%26iu%3D/4140/ostg.clktrk&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=f2bd5c86266ab7f684db698e1f8f0767e577f26c8611423aefea801191142b53 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://urldefense.proofpoint.com/v1/url?u=https://lists.sourceforge.net/lists/listinfo/wix-users&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=68218b7001788b0269a748059c466cd9ab04496b64651e1d91cc0453416bff08 NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- 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. https://urldefense.proofpoint.com/v1/url?u=http://pubads.g.doubleclick.net/gampad/clk?id%3D49501711%26iu%3D/4140/ostg.clktrk&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=f2bd5c86266ab7f684db698e1f8f0767e577f26c8611423aefea801191142b53 ___ WiX-us
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: I have these also: Just in case adding more of them would make the problem go away. And this: xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"; 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\EventLogMessages.dll", but even that gives the same message. I've googled until my googler is sore, can't discover what is wrong. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- 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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[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: I have these also: Just in case adding more of them would make the problem go away. And this: xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"; 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\EventLogMessages.dll", but even that gives the same message. I've googled until my googler is sore, can't discover what is wrong. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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=49501711&iu=/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
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" 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=49501711&iu=/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=49501711&iu=/4140/ostg.c > lktrk ___ > 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=49501711&iu=/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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Having trouble modifying a Built-in WixUI dialog set
There is an example here that might help: http://neilsleightholm.blogspot.co.uk/2008/08/customised-uis-for-wix.html -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: 31 July 2013 21:11 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] Having trouble modifying a Built-in WixUI dialog set I posted this on stackoverflow http://stackoverflow.com/questions/17952469/having-trouble-modifying-a-built-in-wixui-dialog-set with no answers yet, so I thought I would try here. I am trying to hide the license agreement from the built-in WixUI_InstallDir dialog set. I found some helpful instruction http://www.howdoicode.net/2011/09/wix-how-to-hide-license-agreement.html I've added this to the Product.wxs: NOT Installed 1 The next button on the welcome dialog happily goes to the install directory dialog, but the back button of InstallDirDlg goes to the license agreement. Any ideas would be appreciated. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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=49501711&iu=/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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Having trouble modifying a Built-in WixUI dialog set [P]
Classification: Public I had the license agreement in mine but moved the license agreement to the bootstrapper (bundle) Do you have the licenseagreement dialog listed at all? Where is your Next control event for the InstallDirDlg? This is what I have: 1 1 NOT Installed Installed AND PATCH NOT Installed DATABASE_CREATE_SCHEMA = "1" and DATABASE_TEST_CONNECTION = "1" and NOT DATABASE_NAME = "" and NOT Installed NOT Installed CREATE_BACKUP_MIGRATE_CHECKBOX = "1" and NOT Installed NOT Installed WINDOWSPORT_TEST_CONNECTION = "1" and WEBAPPLOGON_TEST_CONNECTION = "1" and NOT Installed NOT Installed NOT Installed and NOT WEBADMIN_USERNAME = "" NOT Installed OR WixUI_InstallMode = "Change" Installed AND NOT PATCH Installed AND PATCH 1 1 1 1 1 -Original Message- From: Tony White [mailto:twh...@ent.com] Sent: July-31-13 4:11 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] Having trouble modifying a Built-in WixUI dialog set I posted this on stackoverflow http://stackoverflow.com/questions/17952469/having-trouble-modifying-a-built-in-wixui-dialog-set with no answers yet, so I thought I would try here. I am trying to hide the license agreement from the built-in WixUI_InstallDir dialog set. I found some helpful instruction http://www.howdoicode.net/2011/09/wix-how-to-hide-license-agreement.html I've added this to the Product.wxs: NOT Installed 1 The next button on the welcome dialog happily goes to the install directory dialog, but the back button of InstallDirDlg goes to the license agreement. Any ideas would be appreciated. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been marked as Public by Steven Ogilvie on July-31-13 4:27:28 PM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Having trouble modifying a Built-in WixUI dialog set
You're going to end up with an InstallDir overlayed with your Publish changes--this is not a recipe for success. The way that works is to take the InstallDir UI from source, modify it to your liking, and that put a in your product.wxs to a unique Id for your customized version of the InstallDir UI. This is the approach I use on the majority of my installers. -- 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 3:11 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] Having trouble modifying a Built-in WixUI dialog set I posted this on stackoverflow http://stackoverflow.com/questions/17952469/having-trouble-modifying-a-built-in-wixui-dialog-set with no answers yet, so I thought I would try here. I am trying to hide the license agreement from the built-in WixUI_InstallDir dialog set. I found some helpful instruction http://www.howdoicode.net/2011/09/wix-how-to-hide-license-agreement.html I've added this to the Product.wxs: NOT Installed 1 The next button on the welcome dialog happily goes to the install directory dialog, but the back button of InstallDirDlg goes to the license agreement. Any ideas would be appreciated. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- 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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Having trouble modifying a Built-in WixUI dialog set
I posted this on stackoverflow http://stackoverflow.com/questions/17952469/having-trouble-modifying-a-built-in-wixui-dialog-set with no answers yet, so I thought I would try here. I am trying to hide the license agreement from the built-in WixUI_InstallDir dialog set. I found some helpful instruction http://www.howdoicode.net/2011/09/wix-how-to-hide-license-agreement.html I've added this to the Product.wxs: NOT Installed 1 The next button on the welcome dialog happily goes to the install directory dialog, but the back button of InstallDirDlg goes to the license agreement. Any ideas would be appreciated. Thanks, Tony This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 2510-2521 and may be legally privileged. The information contained in this Email is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please immediately notify us by telephone and destroy the original message. -- 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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
Classification: Public A.) On a 64 bit machine running 32 bit Office, we install the 32 bit MSI for out Plugins installer and our Client install b) The component and file ID is different for both files one is cmp_filename the other is cmp_filename_x64, and file_filename the other file_filename_x64 and of course the GUID is also different... BUT the actual installed file is the same file name... i.e. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: July-31-13 3:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] A) Ok, then you should probably have a conditional Condition element on the 32 bit install to prevent the 32 bit MSI from installing on a 64 bit PC. B) Knowing that, This will cause both the 64 bit and 32 bit components to have the same ID's but since you won't support both on the same PC it should not be a problem. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 2:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I build the solution twice, once as ReleaseX86 and then again for ReleaseX64 (produces 2 MSI's, i.e. install_x86.msi, install_x64.msi) to answer: Will happen at COMPILE/LINK time, so you will need to build the same project twice. Once as 32 bit and once as 64 bit. To answer: A) do you need to support both 32 bit and 64 bit components on the same PC? No, we only install 1 on a machine, but the machine could be 32 bit or 64 bit hence we have 2 MSI's B) Is this component part of the wixlib, part of your product, or part of a megre module? Sorry this is in the Product.wxs file (this was to ask about the diff about var.Platform vs sys.BUILDARCH C) Are the number and name of destination files identical, just that they are sourced from a different lib folder? Yes the name of the file is the same but the location is different lib\x86 and lib\x64 steve -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: July-31-13 2:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I'm confused... Will happen at COMPILE/LINK time, so you will need to build the same project twice. Once as 32 bit and once as 64 bit. As for I would ask a few things: A) do you need to support both 32 bit and 64 bit components on the same PC? B) Is this component part of the wixlib, part of your product, or part of a megre module? C) Are the number and name of destination files identical, just that they are sourced from a different lib folder? -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 1:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Nuts more files to change roger that, will change :) -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I have a very similar include file in the installer that must build two platforms. The only difference is that I replace $(var.Platform) with $(sys.BUILDARCH). It has worked in production for nearly two years that way. -- 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: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 12:50 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Sigh, every example I see out there in Google land they use And also this? So your saying replace $(var.Platform) with $(sys.BUILDARCH) since the above code should run at runtime... -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 1:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Yes, it appears to be inverted. Also, as the docume
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
A) Ok, then you should probably have a conditional Condition element on the 32 bit install to prevent the 32 bit MSI from installing on a 64 bit PC. B) Knowing that, This will cause both the 64 bit and 32 bit components to have the same ID's but since you won't support both on the same PC it should not be a problem. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 2:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I build the solution twice, once as ReleaseX86 and then again for ReleaseX64 (produces 2 MSI's, i.e. install_x86.msi, install_x64.msi) to answer: Will happen at COMPILE/LINK time, so you will need to build the same project twice. Once as 32 bit and once as 64 bit. To answer: A) do you need to support both 32 bit and 64 bit components on the same PC? No, we only install 1 on a machine, but the machine could be 32 bit or 64 bit hence we have 2 MSI's B) Is this component part of the wixlib, part of your product, or part of a megre module? Sorry this is in the Product.wxs file (this was to ask about the diff about var.Platform vs sys.BUILDARCH C) Are the number and name of destination files identical, just that they are sourced from a different lib folder? Yes the name of the file is the same but the location is different lib\x86 and lib\x64 steve -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: July-31-13 2:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I'm confused... Will happen at COMPILE/LINK time, so you will need to build the same project twice. Once as 32 bit and once as 64 bit. As for I would ask a few things: A) do you need to support both 32 bit and 64 bit components on the same PC? B) Is this component part of the wixlib, part of your product, or part of a megre module? C) Are the number and name of destination files identical, just that they are sourced from a different lib folder? -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 1:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Nuts more files to change roger that, will change :) -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I have a very similar include file in the installer that must build two platforms. The only difference is that I replace $(var.Platform) with $(sys.BUILDARCH). It has worked in production for nearly two years that way. -- 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: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 12:50 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Sigh, every example I see out there in Google land they use And also this? So your saying replace $(var.Platform) with $(sys.BUILDARCH) since the above code should run at runtime... -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 1:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Yes, it appears to be inverted. Also, as the documentation states, $(sys.BUILDARCH) is a better choice than $(var.Platform). -- 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: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, July 31, 2013 12:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] That "should" work, remembering you need both a 32bit and a 64 bit MSI. Though I do think you have the MergRef's inverted based on the condition... -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, July 31, 2013 11:48 AM To: G
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
Classification: Public I build the solution twice, once as ReleaseX86 and then again for ReleaseX64 (produces 2 MSI's, i.e. install_x86.msi, install_x64.msi) to answer: Will happen at COMPILE/LINK time, so you will need to build the same project twice. Once as 32 bit and once as 64 bit. To answer: A) do you need to support both 32 bit and 64 bit components on the same PC? No, we only install 1 on a machine, but the machine could be 32 bit or 64 bit hence we have 2 MSI's B) Is this component part of the wixlib, part of your product, or part of a megre module? Sorry this is in the Product.wxs file (this was to ask about the diff about var.Platform vs sys.BUILDARCH C) Are the number and name of destination files identical, just that they are sourced from a different lib folder? Yes the name of the file is the same but the location is different lib\x86 and lib\x64 steve -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: July-31-13 2:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I'm confused... Will happen at COMPILE/LINK time, so you will need to build the same project twice. Once as 32 bit and once as 64 bit. As for I would ask a few things: A) do you need to support both 32 bit and 64 bit components on the same PC? B) Is this component part of the wixlib, part of your product, or part of a megre module? C) Are the number and name of destination files identical, just that they are sourced from a different lib folder? -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 1:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Nuts more files to change roger that, will change :) -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I have a very similar include file in the installer that must build two platforms. The only difference is that I replace $(var.Platform) with $(sys.BUILDARCH). It has worked in production for nearly two years that way. -- 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: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 12:50 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Sigh, every example I see out there in Google land they use And also this? So your saying replace $(var.Platform) with $(sys.BUILDARCH) since the above code should run at runtime... -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 1:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Yes, it appears to be inverted. Also, as the documentation states, $(sys.BUILDARCH) is a better choice than $(var.Platform). -- 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: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, July 31, 2013 12:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] That "should" work, remembering you need both a 32bit and a 64 bit MSI. Though I do think you have the MergRef's inverted based on the condition... -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, July 31, 2013 11:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Sorry I may have confused the issue by stating how I did it, the main question was does this (or something similar) not work ? Along the lines of -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 17:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Can't use W
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
I'm confused... Will happen at COMPILE/LINK time, so you will need to build the same project twice. Once as 32 bit and once as 64 bit. As for I would ask a few things: A) do you need to support both 32 bit and 64 bit components on the same PC? B) Is this component part of the wixlib, part of your product, or part of a megre module? C) Are the number and name of destination files identical, just that they are sourced from a different lib folder? -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 1:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Nuts more files to change roger that, will change :) -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I have a very similar include file in the installer that must build two platforms. The only difference is that I replace $(var.Platform) with $(sys.BUILDARCH). It has worked in production for nearly two years that way. -- 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: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 12:50 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Sigh, every example I see out there in Google land they use And also this? So your saying replace $(var.Platform) with $(sys.BUILDARCH) since the above code should run at runtime... -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 1:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Yes, it appears to be inverted. Also, as the documentation states, $(sys.BUILDARCH) is a better choice than $(var.Platform). -- 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: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, July 31, 2013 12:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] That "should" work, remembering you need both a 32bit and a 64 bit MSI. Though I do think you have the MergRef's inverted based on the condition... -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, July 31, 2013 11:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Sorry I may have confused the issue by stating how I did it, the main question was does this (or something similar) not work ? Along the lines of -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 17:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me) I am installing 5 Services, they each go into a separate folder off the Services parent folder. They share 8-10 WIXLIBS each (common files for each service, didn't make sense to create new component for each file 5 times) Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything into the Product.wxs since I would be repeating files 5 times 10-20 files... Was able to change 3 other installers from 2 solutions down to 1 solution and able to create x86 and x64 MSI's Might just leave this one alone :( Steve -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: July-31-13 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work arou
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
> That doesn't make much sense because $(var.Platform) is compile time. For an x64 build, it's like you wrote: (and x86 is ) This could be simplified to "VersionNT64" Dave -- 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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
Classification: Public Nuts more files to change roger that, will change :) -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I have a very similar include file in the installer that must build two platforms. The only difference is that I replace $(var.Platform) with $(sys.BUILDARCH). It has worked in production for nearly two years that way. -- 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: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 12:50 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Sigh, every example I see out there in Google land they use And also this? So your saying replace $(var.Platform) with $(sys.BUILDARCH) since the above code should run at runtime... -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 1:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Yes, it appears to be inverted. Also, as the documentation states, $(sys.BUILDARCH) is a better choice than $(var.Platform). -- 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: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, July 31, 2013 12:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] That "should" work, remembering you need both a 32bit and a 64 bit MSI. Though I do think you have the MergRef's inverted based on the condition... -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, July 31, 2013 11:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Sorry I may have confused the issue by stating how I did it, the main question was does this (or something similar) not work ? Along the lines of -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 17:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me) I am installing 5 Services, they each go into a separate folder off the Services parent folder. They share 8-10 WIXLIBS each (common files for each service, didn't make sense to create new component for each file 5 times) Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything into the Product.wxs since I would be repeating files 5 times 10-20 files... Was able to change 3 other installers from 2 solutions down to 1 solution and able to create x86 and x64 MSI's Might just leave this one alone :( Steve -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: July-31-13 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work around the issue with some pre-processing? e.g. You seem to be trying to include both sets of merge module into the msi at compile time then deciding on what to install at runtime when you actually need to decide at compile time. Dave W. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 13:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solut
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
I have a very similar include file in the installer that must build two platforms. The only difference is that I replace $(var.Platform) with $(sys.BUILDARCH). It has worked in production for nearly two years that way. -- 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: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Wednesday, July 31, 2013 12:50 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Sigh, every example I see out there in Google land they use And also this? So your saying replace $(var.Platform) with $(sys.BUILDARCH) since the above code should run at runtime... -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 1:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Yes, it appears to be inverted. Also, as the documentation states, $(sys.BUILDARCH) is a better choice than $(var.Platform). -- 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: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, July 31, 2013 12:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] That "should" work, remembering you need both a 32bit and a 64 bit MSI. Though I do think you have the MergRef's inverted based on the condition... -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, July 31, 2013 11:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Sorry I may have confused the issue by stating how I did it, the main question was does this (or something similar) not work ? Along the lines of -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 17:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me) I am installing 5 Services, they each go into a separate folder off the Services parent folder. They share 8-10 WIXLIBS each (common files for each service, didn't make sense to create new component for each file 5 times) Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything into the Product.wxs since I would be repeating files 5 times 10-20 files... Was able to change 3 other installers from 2 solutions down to 1 solution and able to create x86 and x64 MSI's Might just leave this one alone :( Steve -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: July-31-13 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work around the issue with some pre-processing? e.g. You seem to be trying to include both sets of merge module into the msi at compile time then deciding on what to install at runtime when you actually need to decide at compile time. Dave W. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 13:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solution using the configurations to build x86 MSI x64 MSI Steve -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: July-31-13 1:23 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] You need one set of me
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
Classification: Public Sigh, every example I see out there in Google land they use And also this? So your saying replace $(var.Platform) with $(sys.BUILDARCH) since the above code should run at runtime... -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: July-31-13 1:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Yes, it appears to be inverted. Also, as the documentation states, $(sys.BUILDARCH) is a better choice than $(var.Platform). -- 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: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, July 31, 2013 12:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] That "should" work, remembering you need both a 32bit and a 64 bit MSI. Though I do think you have the MergRef's inverted based on the condition... -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, July 31, 2013 11:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Sorry I may have confused the issue by stating how I did it, the main question was does this (or something similar) not work ? Along the lines of -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 17:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me) I am installing 5 Services, they each go into a separate folder off the Services parent folder. They share 8-10 WIXLIBS each (common files for each service, didn't make sense to create new component for each file 5 times) Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything into the Product.wxs since I would be repeating files 5 times 10-20 files... Was able to change 3 other installers from 2 solutions down to 1 solution and able to create x86 and x64 MSI's Might just leave this one alone :( Steve -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: July-31-13 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work around the issue with some pre-processing? e.g. You seem to be trying to include both sets of merge module into the msi at compile time then deciding on what to install at runtime when you actually need to decide at compile time. Dave W. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 13:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solution using the configurations to build x86 MSI x64 MSI Steve -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: July-31-13 1:23 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] You need one set of merge modules for x64 and another for x86, correct? Use conditional compilation. You don't need all the merge modules in the x86, correct? Why put them there? Or am I missing something? > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com > Date: Tue, 30 Jul 2013 16:19:37 + > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Yup I have the configuration set in the Solution file for my Services > Solution, and in each MergeModule WIXProj I have set up x86/x64 > configurations so it is built twice once for x86 and once for x64 and > placed in different fo
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
Yes, it appears to be inverted. Also, as the documentation states, $(sys.BUILDARCH) is a better choice than $(var.Platform). -- 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: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, July 31, 2013 12:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] That "should" work, remembering you need both a 32bit and a 64 bit MSI. Though I do think you have the MergRef's inverted based on the condition... -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, July 31, 2013 11:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Sorry I may have confused the issue by stating how I did it, the main question was does this (or something similar) not work ? Along the lines of -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 17:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me) I am installing 5 Services, they each go into a separate folder off the Services parent folder. They share 8-10 WIXLIBS each (common files for each service, didn't make sense to create new component for each file 5 times) Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything into the Product.wxs since I would be repeating files 5 times 10-20 files... Was able to change 3 other installers from 2 solutions down to 1 solution and able to create x86 and x64 MSI's Might just leave this one alone :( Steve -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: July-31-13 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work around the issue with some pre-processing? e.g. You seem to be trying to include both sets of merge module into the msi at compile time then deciding on what to install at runtime when you actually need to decide at compile time. Dave W. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 13:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solution using the configurations to build x86 MSI x64 MSI Steve -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: July-31-13 1:23 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] You need one set of merge modules for x64 and another for x86, correct? Use conditional compilation. You don't need all the merge modules in the x86, correct? Why put them there? Or am I missing something? > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com > Date: Tue, 30 Jul 2013 16:19:37 + > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Yup I have the configuration set in the Solution file for my Services > Solution, and in each MergeModule WIXProj I have set up x86/x64 > configurations so it is built twice once for x86 and once for x64 and > placed in different folders wixlib/wixlibx64 (both merge modules and > wixlibs) > > So I have 1 MergeModule project / 1 wixlib project but multiple > configurations to handle the x86/x64 > > Looks like I am pooched... > > Steve > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: July-30-13 12:11 PM > To: General discussion for Windows Installer XML toolset.; David > Connet > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Isn't the win64 setting o
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" 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=49501711&iu=/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=49501711&iu=/4140/ostg.c > lktrk ___ > 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=49501711&iu=/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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
That "should" work, remembering you need both a 32bit and a 64 bit MSI. Though I do think you have the MergRef's inverted based on the condition... -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, July 31, 2013 11:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Sorry I may have confused the issue by stating how I did it, the main question was does this (or something similar) not work ? Along the lines of -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 17:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me) I am installing 5 Services, they each go into a separate folder off the Services parent folder. They share 8-10 WIXLIBS each (common files for each service, didn't make sense to create new component for each file 5 times) Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything into the Product.wxs since I would be repeating files 5 times 10-20 files... Was able to change 3 other installers from 2 solutions down to 1 solution and able to create x86 and x64 MSI's Might just leave this one alone :( Steve -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: July-31-13 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work around the issue with some pre-processing? e.g. You seem to be trying to include both sets of merge module into the msi at compile time then deciding on what to install at runtime when you actually need to decide at compile time. Dave W. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 13:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solution using the configurations to build x86 MSI x64 MSI Steve -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: July-31-13 1:23 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] You need one set of merge modules for x64 and another for x86, correct? Use conditional compilation. You don't need all the merge modules in the x86, correct? Why put them there? Or am I missing something? > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com > Date: Tue, 30 Jul 2013 16:19:37 + > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Yup I have the configuration set in the Solution file for my Services > Solution, and in each MergeModule WIXProj I have set up x86/x64 > configurations so it is built twice once for x86 and once for x64 and > placed in different folders wixlib/wixlibx64 (both merge modules and > wixlibs) > > So I have 1 MergeModule project / 1 wixlib project but multiple > configurations to handle the x86/x64 > > Looks like I am pooched... > > Steve > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: July-30-13 12:11 PM > To: General discussion for Windows Installer XML toolset.; David > Connet > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Isn't the win64 setting on the component so you need to build a 64bit > and a > 32 bit version of each merge module (or wixlib). > This is easily done with a shared .wxs file and a compilation setting. > > I have 32 and 64 bit components all up my build tree just because one package needs a 32 and a 64 bit msi. > > (another) Dave > > > -Original Message- > From: Steven Ogilvie [mailto:steven.ogil...@titus.com] > Sent: 30 July 2013 16:54 > To: David Connet; General discussion forWindows Installer XML toolset. > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [
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" 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=49501711&iu=/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=49501711&iu=/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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
Sorry I may have confused the issue by stating how I did it, the main question was does this (or something similar) not work ? Along the lines of -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 17:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me) I am installing 5 Services, they each go into a separate folder off the Services parent folder. They share 8-10 WIXLIBS each (common files for each service, didn't make sense to create new component for each file 5 times) Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything into the Product.wxs since I would be repeating files 5 times 10-20 files... Was able to change 3 other installers from 2 solutions down to 1 solution and able to create x86 and x64 MSI's Might just leave this one alone :( Steve -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: July-31-13 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work around the issue with some pre-processing? e.g. You seem to be trying to include both sets of merge module into the msi at compile time then deciding on what to install at runtime when you actually need to decide at compile time. Dave W. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 13:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solution using the configurations to build x86 MSI x64 MSI Steve -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: July-31-13 1:23 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] You need one set of merge modules for x64 and another for x86, correct? Use conditional compilation. You don't need all the merge modules in the x86, correct? Why put them there? Or am I missing something? > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com > Date: Tue, 30 Jul 2013 16:19:37 + > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Yup I have the configuration set in the Solution file for my Services > Solution, and in each MergeModule WIXProj I have set up x86/x64 > configurations so it is built twice once for x86 and once for x64 and > placed in different folders wixlib/wixlibx64 (both merge modules and > wixlibs) > > So I have 1 MergeModule project / 1 wixlib project but multiple > configurations to handle the x86/x64 > > Looks like I am pooched... > > Steve > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: July-30-13 12:11 PM > To: General discussion for Windows Installer XML toolset.; David > Connet > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Isn't the win64 setting on the component so you need to build a 64bit > and a > 32 bit version of each merge module (or wixlib). > This is easily done with a shared .wxs file and a compilation setting. > > I have 32 and 64 bit components all up my build tree just because one package needs a 32 and a 64 bit msi. > > (another) Dave > > > -Original Message- > From: Steven Ogilvie [mailto:steven.ogil...@titus.com] > Sent: 30 July 2013 16:54 > To: David Connet; General discussion forWindows Installer XML toolset. > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Sigh same merge modules just compiled under x86 and x64 > > Get the error: > > Error 49 The merge module 'EnterpriseServicesMM_x64' contains a file > identifier, > 'fil2502525491FAEBF0E0D0ED1FE352E76D.9EFC3F5B_3D47_4233_A162_371DEF5D8 > E92', that is duplicated either in another merge module or in a > File/@Id attribute. > File identifiers must be unique. Please change one of the file i
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
Merge modules don't have the concept of "condition". You put the condition on every component in the merge module or you put the condition on the feature(s) that reference the merge modules (and hence the components ). Once merged, a merge module doesn't exist. It's a build time concept not an install time concept. The same applies for wixlibs. No difference at runtime other then the lack of modularization guids and artifiacts in the ModuleSignature and ModuleDependency tables. From: "Steven Ogilvie" Sent: Wednesday, July 31, 2013 11:34 AM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me) I am installing 5 Services, they each go into a separate folder off the Services parent folder. They share 8-10 WIXLIBS each (common files for each service, didn't make sense to create new component for each file 5 times) Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything into the Product.wxs since I would be repeating files 5 times 10-20 files... Was able to change 3 other installers from 2 solutions down to 1 solution and able to create x86 and x64 MSI's Might just leave this one alone :( Steve -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: July-31-13 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-so u rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work around the issue with some pre-processing? e.g. You seem to be trying to include both sets of merge module into the msi at compile time then deciding on what to install at runtime when you actually need to decide at compile time. Dave W. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 13:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solution using the configurations to build x86 MSI x64 MSI Steve -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: July-31-13 1:23 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] You need one set of merge modules for x64 and another for x86, correct? Use conditional compilation. You don't need all the merge modules in the x86, correct? Why put them there? Or am I missing something? > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com > Date: Tue, 30 Jul 2013 16:19:37 + > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Yup I have the configuration set in the Solution file for my Services > Solution, and in each MergeModule WIXProj I have set up x86/x64 > configurations so it is built twice once for x86 and once for x64 and > placed in different folders wixlib/wixlibx64 (both merge modules and > wixlibs) > > So I have 1 MergeModule project / 1 wixlib project but multiple > configurations to handle the x86/x64 > > Looks like I am pooched... > > Steve > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: July-30-13 12:11 PM > To: General discussion for Windows Installer XML toolset.; David > Connet > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Isn't the win64 setting on the component so you need to build a 64bit > and a > 32 bit version of each merge module (or wixlib). > This is easily done with a shared .wxs file and a compilation setting. > > I have 32 and 64 bit components all up my build tree just because one package needs a 32 and a 64 bit msi. > > (another) Dave > > > -Original Message- > From: Steven Ogilvie [mailto:steven.ogil...@titus.com] > Sent: 30 July 2013 16:54 > To: David Connet; General discussion forWindows Installer XML toolset. > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Sigh same merge modules just compiled under
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
Classification: Public Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me) I am installing 5 Services, they each go into a separate folder off the Services parent folder. They share 8-10 WIXLIBS each (common files for each service, didn't make sense to create new component for each file 5 times) Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything into the Product.wxs since I would be repeating files 5 times 10-20 files... Was able to change 3 other installers from 2 solutions down to 1 solution and able to create x86 and x64 MSI's Might just leave this one alone :( Steve -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: July-31-13 12:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work around the issue with some pre-processing? e.g. You seem to be trying to include both sets of merge module into the msi at compile time then deciding on what to install at runtime when you actually need to decide at compile time. Dave W. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 13:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solution using the configurations to build x86 MSI x64 MSI Steve -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: July-31-13 1:23 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] You need one set of merge modules for x64 and another for x86, correct? Use conditional compilation. You don't need all the merge modules in the x86, correct? Why put them there? Or am I missing something? > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com > Date: Tue, 30 Jul 2013 16:19:37 + > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Yup I have the configuration set in the Solution file for my Services > Solution, and in each MergeModule WIXProj I have set up x86/x64 > configurations so it is built twice once for x86 and once for x64 and > placed in different folders wixlib/wixlibx64 (both merge modules and > wixlibs) > > So I have 1 MergeModule project / 1 wixlib project but multiple > configurations to handle the x86/x64 > > Looks like I am pooched... > > Steve > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: July-30-13 12:11 PM > To: General discussion for Windows Installer XML toolset.; David > Connet > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Isn't the win64 setting on the component so you need to build a 64bit > and a > 32 bit version of each merge module (or wixlib). > This is easily done with a shared .wxs file and a compilation setting. > > I have 32 and 64 bit components all up my build tree just because one package needs a 32 and a 64 bit msi. > > (another) Dave > > > -Original Message- > From: Steven Ogilvie [mailto:steven.ogil...@titus.com] > Sent: 30 July 2013 16:54 > To: David Connet; General discussion forWindows Installer XML toolset. > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Sigh same merge modules just compiled under x86 and x64 > > Get the error: > > Error 49 The merge module 'EnterpriseServicesMM_x64' contains a file > identifier, > 'fil2502525491FAEBF0E0D0ED1FE352E76D.9EFC3F5B_3D47_4233_A162_371DEF5D8 > E92', that is duplicated either in another merge module or in a > File/@Id attribute. > File identifiers must be unique. Please change one of the file identifiers > to a different value. C:\Dev\ Setup\Services_Setup\Product.wxs282 > 1 Services_Setup > > Title="Merge modules for 32 bit OS" > Level="1" > Display="expand" > ConfigurableDirectory="DIRECTORY_PATH_SERVICES"> > ... > > > > > > Title="Merge modules for 64 bit OS" >
Re: [WiX-users] Need to help! Uninstall the MSI on windows 7
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=49501711&iu=/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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
I write installation sources all the time where the very same WXS files (and in fact the very same WIXPROJ files) are used to make both configurations. A very small amount of conditionals goes a long ways to making that work. > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net > Date: Wed, 31 Jul 2013 12:55:27 + > Subject: Re: [WiX-users] Need help, how to put a condition on a merge module > in Product.wxs [P] > > Classification: Public > I originally have two solutions for the Services installer, in the x86 > product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the > 5 x64 merge modules... > So there are two sets of merge modules x86 compiled and x64 compiled > > I am trying to make 1 solution using the configurations to build x86 MSI x64 > MSI > > Steve > > -Original Message- > From: Blair Murri [mailto:os...@live.com] > Sent: July-31-13 1:23 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Need help, how to put a condition on a merge module > in Product.wxs [P] > > You need one set of merge modules for x64 and another for x86, correct? > > Use conditional compilation. You don't need all the merge modules in the x86, > correct? Why put them there? > > Or am I missing something? > > > From: steven.ogil...@titus.com > > To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com > > Date: Tue, 30 Jul 2013 16:19:37 + > > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > > module in Product.wxs [P] > > > > Classification: Public > > Yup I have the configuration set in the Solution file for my Services > > Solution, and in each MergeModule WIXProj I have set up x86/x64 > > configurations so it is built twice once for x86 and once for x64 and > > placed in different folders wixlib/wixlibx64 (both merge modules and > > wixlibs) > > > > So I have 1 MergeModule project / 1 wixlib project but multiple > > configurations to handle the x86/x64 > > > > Looks like I am pooched... > > > > Steve > > > > -Original Message- > > From: David Watson [mailto:dwat...@sdl.com] > > Sent: July-30-13 12:11 PM > > To: General discussion for Windows Installer XML toolset.; David > > Connet > > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > > module in Product.wxs [P] > > > > Isn't the win64 setting on the component so you need to build a 64bit > > and a > > 32 bit version of each merge module (or wixlib). > > This is easily done with a shared .wxs file and a compilation setting. > > > > I have 32 and 64 bit components all up my build tree just because one > > package needs a 32 and a 64 bit msi. > > > > (another) Dave > > > > > > -Original Message- > > From: Steven Ogilvie [mailto:steven.ogil...@titus.com] > > Sent: 30 July 2013 16:54 > > To: David Connet; General discussion forWindows Installer XML toolset. > > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > > module in Product.wxs [P] > > > > Classification: Public > > Sigh same merge modules just compiled under x86 and x64 > > > > Get the error: > > > > Error 49 The merge module 'EnterpriseServicesMM_x64' contains a > > file > > identifier, > > 'fil2502525491FAEBF0E0D0ED1FE352E76D.9EFC3F5B_3D47_4233_A162_371DEF5D8 > > E92', that is duplicated either in another merge module or in a > > File/@Id attribute. > > File identifiers must be unique. Please change one of the file identifiers > > to a different value. C:\Dev\ Setup\Services_Setup\Product.wxs > > 282 > > 1 Services_Setup > > > > > Title="Merge modules for 32 bit OS" > > Level="1" > > Display="expand" > > ConfigurableDirectory="DIRECTORY_PATH_SERVICES"> > > ... > > > > > > > > > > > > > Title="Merge modules for 64 bit OS" > > Level="1" > > Display="expand" > > ConfigurableDirectory="DIRECTORY_PATH_SERVICES"> > > ... > > > > > > > > > > > > ... > > > SourceFile="$(env.SharedServices)\Installers\wixlib\ServicesMergeModule.msm" > > Language="1033"/> ... > > > SourceFile="$(env.SharedServices)\Installers\wixlibx64\ServicesMergeMo > > dule.ms > > m" Language="1033"/> > > > > -Original Message- > > From: David Connet [mailto:d...@agilityrecordbook.com] > > Sent: July-30-13 11:10 AM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > > module in Product.wxs [P] > > > > Assign them to a feature and condition the feature. > > > > Dave > > > > > > > > - Original Message - > > From: Steven Ogilvie > > To: General discussion for Windows Installer XML toolset. > > > > Cc: > > Sent: Tuesday, July 30, 2013 7:16 AM > > Subject: Re: [WiX-users] Need help, how to put a condition on a merge
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
I did it by not using merge modules, I used pure wixlibs. http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ So my components are pulled into the msi by ComponentGroupRef not by MergeID. I only have the relevant bitness wixlib referenced in the wixproj. Can you work around the issue with some pre-processing? e.g. You seem to be trying to include both sets of merge module into the msi at compile time then deciding on what to install at runtime when you actually need to decide at compile time. Dave W. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 31 July 2013 13:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solution using the configurations to build x86 MSI x64 MSI Steve -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: July-31-13 1:23 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] You need one set of merge modules for x64 and another for x86, correct? Use conditional compilation. You don't need all the merge modules in the x86, correct? Why put them there? Or am I missing something? > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com > Date: Tue, 30 Jul 2013 16:19:37 + > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Yup I have the configuration set in the Solution file for my Services > Solution, and in each MergeModule WIXProj I have set up x86/x64 > configurations so it is built twice once for x86 and once for x64 and > placed in different folders wixlib/wixlibx64 (both merge modules and > wixlibs) > > So I have 1 MergeModule project / 1 wixlib project but multiple > configurations to handle the x86/x64 > > Looks like I am pooched... > > Steve > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: July-30-13 12:11 PM > To: General discussion for Windows Installer XML toolset.; David > Connet > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Isn't the win64 setting on the component so you need to build a 64bit > and a > 32 bit version of each merge module (or wixlib). > This is easily done with a shared .wxs file and a compilation setting. > > I have 32 and 64 bit components all up my build tree just because one package needs a 32 and a 64 bit msi. > > (another) Dave > > > -Original Message- > From: Steven Ogilvie [mailto:steven.ogil...@titus.com] > Sent: 30 July 2013 16:54 > To: David Connet; General discussion forWindows Installer XML toolset. > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Sigh same merge modules just compiled under x86 and x64 > > Get the error: > > Error 49 The merge module 'EnterpriseServicesMM_x64' contains a file > identifier, > 'fil2502525491FAEBF0E0D0ED1FE352E76D.9EFC3F5B_3D47_4233_A162_371DEF5D8 > E92', that is duplicated either in another merge module or in a > File/@Id attribute. > File identifiers must be unique. Please change one of the file identifiers > to a different value. C:\Dev\ Setup\Services_Setup\Product.wxs282 > 1 Services_Setup > > Title="Merge modules for 32 bit OS" > Level="1" > Display="expand" > ConfigurableDirectory="DIRECTORY_PATH_SERVICES"> > ... > > > > > > Title="Merge modules for 64 bit OS" > Level="1" > Display="expand" > ConfigurableDirectory="DIRECTORY_PATH_SERVICES"> > ... > > > > > > ... > SourceFile="$(env.SharedServices)\Installers\wixlib\ServicesMergeModule.msm" > Language="1033"/> ... > SourceFile="$(env.SharedServices)\Installers\wixlibx64\ServicesMergeMo > dule.ms > m" Language="1033"/> > > -Original Message- > From: David Connet [mailto:d...@agilityrecordbook.com] > Sent: July-30-13 11:10 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Assign them to a feature and condition the feature. > > Dave > > > > - Original Message - > From: Steven Ogilvie > To: General discussion for Windows Installer XML toolset. > > Cc: > Sent: Tuesday, July 30, 2013 7:16
[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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [Patch] Best practice using fragments
Thank you for the response. It is very helpful. Phill -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-Best-practice-using-fragments-tp7587660p7587722.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=49501711&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]
Classification: Public I originally have two solutions for the Services installer, in the x86 product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the 5 x64 merge modules... So there are two sets of merge modules x86 compiled and x64 compiled I am trying to make 1 solution using the configurations to build x86 MSI x64 MSI Steve -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: July-31-13 1:23 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P] You need one set of merge modules for x64 and another for x86, correct? Use conditional compilation. You don't need all the merge modules in the x86, correct? Why put them there? Or am I missing something? > From: steven.ogil...@titus.com > To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com > Date: Tue, 30 Jul 2013 16:19:37 + > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Yup I have the configuration set in the Solution file for my Services > Solution, and in each MergeModule WIXProj I have set up x86/x64 > configurations so it is built twice once for x86 and once for x64 and > placed in different folders wixlib/wixlibx64 (both merge modules and > wixlibs) > > So I have 1 MergeModule project / 1 wixlib project but multiple > configurations to handle the x86/x64 > > Looks like I am pooched... > > Steve > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: July-30-13 12:11 PM > To: General discussion for Windows Installer XML toolset.; David > Connet > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Isn't the win64 setting on the component so you need to build a 64bit > and a > 32 bit version of each merge module (or wixlib). > This is easily done with a shared .wxs file and a compilation setting. > > I have 32 and 64 bit components all up my build tree just because one package > needs a 32 and a 64 bit msi. > > (another) Dave > > > -Original Message- > From: Steven Ogilvie [mailto:steven.ogil...@titus.com] > Sent: 30 July 2013 16:54 > To: David Connet; General discussion forWindows Installer XML toolset. > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > Sigh same merge modules just compiled under x86 and x64 > > Get the error: > > Error 49 The merge module 'EnterpriseServicesMM_x64' contains a file > identifier, > 'fil2502525491FAEBF0E0D0ED1FE352E76D.9EFC3F5B_3D47_4233_A162_371DEF5D8 > E92', that is duplicated either in another merge module or in a > File/@Id attribute. > File identifiers must be unique. Please change one of the file identifiers > to a different value. C:\Dev\ Setup\Services_Setup\Product.wxs282 > 1 Services_Setup > > Title="Merge modules for 32 bit OS" > Level="1" > Display="expand" > ConfigurableDirectory="DIRECTORY_PATH_SERVICES"> > ... > > > > > > Title="Merge modules for 64 bit OS" > Level="1" > Display="expand" > ConfigurableDirectory="DIRECTORY_PATH_SERVICES"> > ... > > > > > > ... > SourceFile="$(env.SharedServices)\Installers\wixlib\ServicesMergeModule.msm" > Language="1033"/> ... > SourceFile="$(env.SharedServices)\Installers\wixlibx64\ServicesMergeMo > dule.ms > m" Language="1033"/> > > -Original Message- > From: David Connet [mailto:d...@agilityrecordbook.com] > Sent: July-30-13 11:10 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Assign them to a feature and condition the feature. > > Dave > > > > - Original Message - > From: Steven Ogilvie > To: General discussion for Windows Installer XML toolset. > > Cc: > Sent: Tuesday, July 30, 2013 7:16 AM > Subject: Re: [WiX-users] Need help, how to put a condition on a merge > module in Product.wxs [P] > > Classification: Public > The 5 merge modules have of > about 10 wixlibs The files in the MergeModules and WixLibs are built > as AnyCPU however since I need to install the services for 64 bit OS > and 32 bit OS I need two MSI's one for 32 and one for 64 bit > > So I am not using any binary files that are specific for 32 bit or 64 bit, I > just need to include the MergeModules in 1 product.wxs file The Merge Modules > themselves are built x86 and x64 and are located in two different folders... > > So the question is, HOW do I conditionally install the merge modules based on > the OS bitness? > > Thanks, > > Steve > > ---
