[WiX-users] heat.exe(0,0): error HEAT5307: Build failed.
Hi All, I've just reinstalled a new laptop with VS2008, Wix3.5 but now when I try build my projects the setup projects fail to build with the following error: heat.exe(0,0): error HEAT5307: Build failed. All the links I see on the internet refer to C++ projects. These however are C# projects. It feels like I must be missing something? Perhaps a patch? I'm running Windows 7 Home Premium on a Core i7 with 8G ram. Thanks, Peter --- Peter Solomon -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Condition based on a string in custom action
Unless I'm totally off base, the line provided does persist ARPINSTALLLOCATION in the unistall environment (it's being explicitly set after CostFinalize regardless of whether this is an initial installation, repair, an update, or a removal.) Am I mistaken? As for CUSTOMDIR, I didn't provide those lines because I didn't think they were relevant... but it too has been explicitly set ... I store the value in the registry when the product is installed, seed with that value from the key retrieved if/when it is present (during updates, removals) - and when the value is not present (initial installation) I provide a default value which the person running the installation can override. What I'm trying to accomplish: finding the proper syntax for the 3rd condition I want to put on myCustAct: ARPINSTALLLOCATION must contain var.ProductName in order for myCustAct to execute. I've tried: and a handful of similar lines for the condition, but regardless of what I specify, MyCustAct always executes (as if the 3rd condition doesn't exist) when I'm removing a previous installation... IF ARPINSTALLLOCATION wasn't persisted, I would expect the condition to always fail (as it would never contain my application's name) but it's doing the opposite, it's always succeeding! Even when the application name isn't present in the path ... hence my problem. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Condition-based-on-a-string-in-custom-action-tp6739641p6740584.html Sent from the wix-users mailing list archive at Nabble.com. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Burn - Use of ARPSYSTEMCOMPONENT To Suppress MSI Files from Add/Remove Programs - Email found in subject
PS: The reason WiX toolset doesn't set ARPSYSTEMCOMPONENT yet is because I wanted to leave everyone an easy escape hatch in the case that Burn got confused and failed to uninstall or upgrade a version of WiX v3.6. When I trust Burn enough (which is pretty soon actually), we'll set ARPSYSTEMCOMPONENT and there will be a single "WiX Toolset v3.6" ARP entry that points at Burn. On Mon, Aug 29, 2011 at 6:05 PM, Bob Arnson wrote: > On 29-Aug-11 18:47, Shaun Hayward wrote: > > My impression that ARPSYSTEMCOMPONENT told the MSIEXEC not to write any > ARP registry entries came from an MSDN blog from some 6 years ago: > > > > http://blogs.msdn.com/b/heaths/archive/2005/08/05/448198.aspx > > > > So the information may not be correct. > > It's correct, just vague. ARPSYSTEMCOMPONENT tells MSI to write -- in > addition to the ARP registry values it normally writes -- a value that > says "don't show me." > > > Ultimately I'm looking to see if use of ARPSYSTEMCOMPONENT is the > appropriate practice to suppress the MSI creating an ARP entry when using > Burn (which also creates an ARP entry). Or is there another practice? > > It is, as long as you're aware of what it entails (see Heath's blog for > posts about it). I recommend putting ARPSYSTEMCOMPONENT in an > MsiProperty element under the package. That way, admins who want to > install the .msis "naked" (without Burn) still get ARP entries. > > > The WiX installer itself doesn't use ARPSYSTEMCOMPONENT and doesn't > suffer from a double-entry in ARP. I'm interested in the mechanism that it > is using. > > It does. One is "WiX Toolset v3.6..0" -- that's Burn's entry -- and > the other is "WiX Toolset v3.6..0 MSI Package." Eventually, the > latter will go away when the .msi package gets ARPSYSTEMCOMPONENT. > > -- > sig://boB > http://joyofsetup.com/ > > > > -- > Special Offer -- Download ArcSight Logger for FREE! > Finally, a world-class log management solution at an even better > price-free! And you'll get a free "Love Thy Logs" t-shirt when you > download Logger. Secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsisghtdev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Changing the default WixStandardBootstrapperApplication.RtfLicense
On 29-Aug-11 11:15, Sheehan, Andrew wrote: > Does v3.6 support the indication/usage of a custom EULA/License file? Yes. See "Specifying the WiX Standard Bootstrapper Application License" in wix.chm. -- sig://boB http://joyofsetup.com/ -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Burn - Use of ARPSYSTEMCOMPONENT To Suppress MSI Files from Add/Remove Programs - Email found in subject
On 29-Aug-11 18:47, Shaun Hayward wrote: > My impression that ARPSYSTEMCOMPONENT told the MSIEXEC not to write any ARP > registry entries came from an MSDN blog from some 6 years ago: > > http://blogs.msdn.com/b/heaths/archive/2005/08/05/448198.aspx > > So the information may not be correct. It's correct, just vague. ARPSYSTEMCOMPONENT tells MSI to write -- in addition to the ARP registry values it normally writes -- a value that says "don't show me." > Ultimately I'm looking to see if use of ARPSYSTEMCOMPONENT is the appropriate > practice to suppress the MSI creating an ARP entry when using Burn (which > also creates an ARP entry). Or is there another practice? It is, as long as you're aware of what it entails (see Heath's blog for posts about it). I recommend putting ARPSYSTEMCOMPONENT in an MsiProperty element under the package. That way, admins who want to install the .msis "naked" (without Burn) still get ARP entries. > The WiX installer itself doesn't use ARPSYSTEMCOMPONENT and doesn't suffer > from a double-entry in ARP. I'm interested in the mechanism that it is using. It does. One is "WiX Toolset v3.6..0" -- that's Burn's entry -- and the other is "WiX Toolset v3.6..0 MSI Package." Eventually, the latter will go away when the .msi package gets ARPSYSTEMCOMPONENT. -- sig://boB http://joyofsetup.com/ -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Burn - Use of ARPSYSTEMCOMPONENT To Suppress MSI Files from Add/Remove Programs - Email found in subject
Thanks, Phil. My impression that ARPSYSTEMCOMPONENT told the MSIEXEC not to write any ARP registry entries came from an MSDN blog from some 6 years ago: http://blogs.msdn.com/b/heaths/archive/2005/08/05/448198.aspx So the information may not be correct. Ultimately I'm looking to see if use of ARPSYSTEMCOMPONENT is the appropriate practice to suppress the MSI creating an ARP entry when using Burn (which also creates an ARP entry). Or is there another practice? The WiX installer itself doesn't use ARPSYSTEMCOMPONENT and doesn't suffer from a double-entry in ARP. I'm interested in the mechanism that it is using. Shaun Hayward | Senior Software Developer | Omnivex | 905.761.6640 ext 429 | www.omnivex.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Monday, August 29, 2011 6:12 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX Burn - Use of ARPSYSTEMCOMPONENT To Suppress MSI Files from Add/Remove Programs - Email found in subject ARPSYSTEMCOMPONENT is just a property you set in the property table of the MSI, like any other property. There's no need for anything special to set it. " As I understand this property of MSI files, it will prevent the installation from writing any registry entries for the MSI in Add/Remove Programs." No - it still writes the registry entries. It just means you won't see your MSI shown in Add/Remove Programs. Phil Wilson -Original Message- From: Shaun Hayward [mailto:shayw...@omnivex.com] Sent: Monday, August 29, 2011 2:14 PM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] WiX Burn - Use of ARPSYSTEMCOMPONENT To Suppress MSI Files from Add/Remove Programs With thanks to Tobias and Cody, I'm making progress on WiX Burn with a managed WPF UI. I've used WiX to create an MSI and Burn to create a bootstrapper for it. After installing with the bootstrapper, I have two entries in Add/Remove programs: one for the MSI, one for the bootstrapper. There have been some messages suggesting the use of ARPSYSTEMCOMPONENT in the MSI to suppress its appearance in ARP. As I understand this property of MSI files, it will prevent the installation from writing any registry entries for the MSI in Add/Remove Programs. But I don't see it in the WiX 3.6 MSI, which uses Burn + WPF for deployment. How does Burn suppress the MSI entry in ARP when installing WiX 3.6 and (most importantly) what is the "supported" or "official" or "recommended" way of suppressing MSI entries with our own Burn-based solutions? Many thanks - Shaun The information in this e-mail is intended solely for the addressee and access by anyone else is unauthorized. Omnivex accepts no liability for the content of this e-mail, or for the consequences of any actions taken on the basis of the information provided. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. Omnivex makes no warranties, express or implied and is not responsible for errors or omissions. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even be
Re: [WiX-users] WiX Burn - Use of ARPSYSTEMCOMPONENT To Suppress MSI Files from Add/Remove Programs
ARPSYSTEMCOMPONENT is just a property you set in the property table of the MSI, like any other property. There's no need for anything special to set it. " As I understand this property of MSI files, it will prevent the installation from writing any registry entries for the MSI in Add/Remove Programs." No - it still writes the registry entries. It just means you won't see your MSI shown in Add/Remove Programs. Phil Wilson -Original Message- From: Shaun Hayward [mailto:shayw...@omnivex.com] Sent: Monday, August 29, 2011 2:14 PM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] WiX Burn - Use of ARPSYSTEMCOMPONENT To Suppress MSI Files from Add/Remove Programs With thanks to Tobias and Cody, I'm making progress on WiX Burn with a managed WPF UI. I've used WiX to create an MSI and Burn to create a bootstrapper for it. After installing with the bootstrapper, I have two entries in Add/Remove programs: one for the MSI, one for the bootstrapper. There have been some messages suggesting the use of ARPSYSTEMCOMPONENT in the MSI to suppress its appearance in ARP. As I understand this property of MSI files, it will prevent the installation from writing any registry entries for the MSI in Add/Remove Programs. But I don't see it in the WiX 3.6 MSI, which uses Burn + WPF for deployment. How does Burn suppress the MSI entry in ARP when installing WiX 3.6 and (most importantly) what is the "supported" or "official" or "recommended" way of suppressing MSI entries with our own Burn-based solutions? Many thanks - Shaun The information in this e-mail is intended solely for the addressee and access by anyone else is unauthorized. Omnivex accepts no liability for the content of this e-mail, or for the consequences of any actions taken on the basis of the information provided. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. Omnivex makes no warranties, express or implied and is not responsible for errors or omissions. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Condition based on a string in custom action
ARPINSTALLLOCATION is a property that people set to make their install location visible via supported MSI APIs. It doesn't get persisted into the uninstall environment unless you persist it, and the same is true of CUSTOMDIR. What are you trying to accomplish here? Phil Wilson -Original Message- From: Mark [mailto:m...@rcsal.com] Sent: Monday, August 29, 2011 2:10 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Condition based on a string in custom action have tried with and without CDATA tags, but can't get the behavior I want regardless of what I do! http://schemas.microsoft.com/wix/2006/wi";> ... ... Installed AND NOT UPGRADINGPRODUCTCODE AND (ARPINSTALLLOCATION >< $(var.ProductName)) ... The installation works beautifully, myCustAct is properly ignored on installations and upgrades (as expected), but when doing a removal: myCustAct always runs regardless of whether or not ARPINSTALLLOCATION contains the var.ProductName !!! It should only happen when the product name is found in (a part of) the ARPINSTALLLOCATION string ... can someone clue me in on how to correct this to get the behavior I'm after? I've tried: with and without quotes, and while the installation always builds and runs properly, I'm not getting the proper behavior on removal. :( Help? :) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Condition-based-on-a-string-in-custom-action-tp6739641p6739641.html Sent from the wix-users mailing list archive at Nabble.com. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Condition based on a string in custom action
have tried with and without CDATA tags, but can't get the behavior I want regardless of what I do! http://schemas.microsoft.com/wix/2006/wi";> ... ... Installed AND NOT UPGRADINGPRODUCTCODE AND (ARPINSTALLLOCATION >< $(var.ProductName)) ... The installation works beautifully, myCustAct is properly ignored on installations and upgrades (as expected), but when doing a removal: myCustAct always runs regardless of whether or not ARPINSTALLLOCATION contains the var.ProductName !!! It should only happen when the product name is found in (a part of) the ARPINSTALLLOCATION string ... can someone clue me in on how to correct this to get the behavior I'm after? I've tried: with and without quotes, and while the installation always builds and runs properly, I'm not getting the proper behavior on removal. :( Help? :) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Condition-based-on-a-string-in-custom-action-tp6739641p6739641.html Sent from the wix-users mailing list archive at Nabble.com. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX Burn - Use of ARPSYSTEMCOMPONENT To Suppress MSI Files from Add/Remove Programs
With thanks to Tobias and Cody, I'm making progress on WiX Burn with a managed WPF UI. I've used WiX to create an MSI and Burn to create a bootstrapper for it. After installing with the bootstrapper, I have two entries in Add/Remove programs: one for the MSI, one for the bootstrapper. There have been some messages suggesting the use of ARPSYSTEMCOMPONENT in the MSI to suppress its appearance in ARP. As I understand this property of MSI files, it will prevent the installation from writing any registry entries for the MSI in Add/Remove Programs. But I don't see it in the WiX 3.6 MSI, which uses Burn + WPF for deployment. How does Burn suppress the MSI entry in ARP when installing WiX 3.6 and (most importantly) what is the "supported" or "official" or "recommended" way of suppressing MSI entries with our own Burn-based solutions? Many thanks - Shaun The information in this e-mail is intended solely for the addressee and access by anyone else is unauthorized. Omnivex accepts no liability for the content of this e-mail, or for the consequences of any actions taken on the basis of the information provided. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. Omnivex makes no warranties, express or implied and is not responsible for errors or omissions. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Install other features in repair mode - Cond. statement problem
Hi, I want the user to allow to reselect features on the repair mode. He should be able to select other features (this is no problem since no other files will be installed, but the custom actions are different depending on the selected features). This works already by using Custom UI and the featuretree. But the following conditional expression does not evaluate true: Can anyone help me? I know the MSDN page "Conditional Statement Syntax" and as far as I understand, &_MYFEATURE should evaluate 3 if the feature is selected in repair mode. Is it a bug or a human failure? BTW: I'm using Wix 2.0. Thank you ;) Marc -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX-users Digest, Vol 63, Issue 59
> · What changes should I make in TFSBuild.proj files? The WiX solution is integrated like other solution into TFSBuild. Add the the needed SolutionToBuild + configurationToBuild. E.g that should be something like following: Release x86 > · What changes should I make in Client Installer.wixproj file? No changes needed if you install WiX on Build machine. If you check in sources into TFS see http://wix.sourceforge.net/manual-wix3/daily_builds.htm Regards, Tobias PS: please communicate directly with the mailing list as topics like Re: WiX-users Digest, Vol 63, Issue 59 start a new Topic instead of continuation an existing one. -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] UI Sequence table in for advertised-shortcut triggered repair
In general, you can't assume the UI is going to run for a repair. For example, running "Repair" from the Control Panel button runs the repair in "Basic" mode with only the basic progress dialog showing. It works from the MaintenanceTypeDlg when you press the "Change" button off Control Panel because the full UI is run. -- John Merryweather Cooper Jack Henry & Associates, Inc. (Premier Tech, Inc.) Build & Install Engineer - jXchange Office: 913-341-3434 x791011 jocoo...@jackhenry.com -Original Message- From: Sameer Arora [mailto:arora...@gmail.com] Sent: Sunday, August 28, 2011 4:32 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] UI Sequence table in for advertised-shortcut triggered repair My scenario is that target for an advertised shortcut is absent. If clicks the shortcut, Windows MSI triggers a repair with parameters REINSTALL=DefaultFeature REINSTALLMODE=pocmus. As part of this repair, the installation sequence seems to skip UI Execute sequence as I see from the log: Action start 9:06:26: INSTALL. MSI (s) (B8:8C) [09:06:26:945]: Running ExecuteSequence ... However, if user performs repair from Add/Remove program, the UI sequence does get triggered Action start 9:06:45: INSTALL. MSI (c) (A8:9C) [09:06:45:601]: UI Sequence table 'InstallUISequence' is present and populated. MSI (c) (A8:9C) [09:06:45:601]: Running UISequence Why is UI sequence table missing/empty when repair is triggered by the advertised shortcut? And is there a way that repair both from ARP and shortcut follow the same UI sequence ? Thank you for any pointers, Sameer -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ 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. -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Changing the default WixStandardBootstrapperApplication.RtfLicense
Hello All, Does v3.6 support the indication/usage of a custom EULA/License file? http://schemas.microsoft.com/wix/2006/wi";> removed for brevity -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Application size doubles when doing repair from ARP
Hi, I am working on a Wix3.0 installer, This installer is having one driver of 54MB to be copied in the user's temp folder before installation, and delete the same after installation from the temp folder. When I am doing repair from the control panel , i am observing that the size gets double after the repair operaion in the case when I am deleting the temp driver folder through custom action after "InstallFinalize" sequence. But when I am sequencing the same custom action after "RemoveExixtingProduct", the folder is not getting deleted bacause of the false value returned by Directory.Exist(path)but size remains the same as earlier. 1.Sequence when size getting double 2.Sequence when size is ok but folder path is not found. where, custom action "MyTempDriverDelete" is performing the deletion operation of the temp driver folder. i am confused on sequence to be assigned, please guide me Thanks, Sandeep -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Simpler Update possible?
You can do this yourself by using the upgrade table and to check for the product version you are looking for and only set the property. You can then use this property to set an installation condition to display a message that the pervious product must be manually removed before continuing. Please keep in mind this has nothing to do with WIX. As stated many times in this forum, WIX is only method used to create the resulting MSI. For further instructions on using the upgrade table, please refer to the MSI documentation on how the Upgrade table works. You can then use this information to get WIX to create the table the way you need it. Mat Skildum -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Simpler Update possible?
Hi, I am wondering if there is any way to have Wix check if the product is already installed (irrespective of the version), if so ask the user to uninstall it manually (or ask the user if he wants it to be uninstalled by Wix if possible). Then Wix would just do a full installation as if it was the first time the product was installed (since the uninstall would have removed everything). This way I could use the "Initial Run" harvesting through Paraffin as part of every build as the component GUIDs won't matter, rather than using the -update switch. Is this possible or am I stuck with the Major update process? Thanks, Andreas -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
