[WiX-users] decompile burn exe
Hi, I know it is possible to decompile msi file using dark.exe. Is it possible to decompile exe file created with burn.exe?When I run dark.exe passing the exe file as parameter I get the error below: dark.exe : error DARK0001 : Value cannot be null.Parameter name: path1 Exception Type: System.ArgumentNullException Stack Trace: at System.IO.Path.Combine(String path1, String path2) at Microsoft.Tools.WindowsInstallerXml.Unbinder.UnbindBundle(String bundleFile, String exportBasePath) at Microsoft.Tools.WindowsInstallerXml.Unbinder.Unbind(String file, OutputType outputType, String exportBasePath) at Microsoft.Tools.WindowsInstallerXml.Tools.Dark.Run(String[] args) How can I decompile exe file create with burn.exe? Thank you,Martin -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] major upgrade from per-client to per-machine install
Hi everyone, Is there a way to detect per-user installation and so that per-machine install is prevented unless the per-user one is uninstalled first? Thank you, Martin Kulov From: mar...@kulov.net To: wix-users@lists.sourceforge.net Date: Tue, 11 Oct 2011 21:01:23 + Subject: Re: [WiX-users] major upgrade from per-client to per-machine install Thanks Rob, Is there a way to detect this situation and prevent the per machine installation in such case? Thanks,Martin From: r...@robmensching.com Date: Tue, 11 Oct 2011 05:56:50 -0700 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] major upgrade from per-client to per-machine install Sadly, Windows Installer doesn't support that. On Mon, Oct 10, 2011 at 9:23 AM, Martin Kulov mar...@kulov.net wrote: Hi, (moving this to a new thread) I have an existing MSI that needs to be MajorUpgrade'd from per client to per machine installation.Right now installing the latest bits results in two versions of the program being installed side by side.This does not work for at all. How can I remove the existing per-user installation during MajorUpgrade so that the new per-machine installation can be installed instead? Thanks a lot!Martin -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] major upgrade from per-client to per-machine install
Thanks Peter! My intention is to prevent the install of per-machine msi until the user uninstalls his per-user installation. Thanks for the pointers into MSI API. I will take a look into that. Best,Martin Date: Thu, 13 Oct 2011 11:01:00 +0100 From: pshirtcli...@sdl.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] major upgrade from per-client to per-machine install Which per-user one ? There could be multiple per-user installations on a machine. You'd have to be an admin to detect the per-user installation of another user. The other users might not be too happy if someone came along and removed their installation if it had some user-specific configuration/customisations that weren't carried over to the new per-machine installation. It sounds like the kind of thing that ought to be sorted out manually, rather than automatically. That said, if your environment means this kind of thing would be ok, then you can enumerate per-user installations with the MSI API call MsiEnumProductsEx() (or DTF equivalent, if there is one) and passing the appropriate context arguments. This would only detect that such products exist. MsiConfigureProductEx could then be used to remove them but I wouldn't do this in an installer... maybe as part of a chainer. -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: 13 October 2011 10:47 To: wix-users Subject: Re: [WiX-users] major upgrade from per-client to per-machine install Hi everyone, Is there a way to detect per-user installation and so that per-machine install is prevented unless the per-user one is uninstalled first? Thank you, Martin Kulov From: mar...@kulov.net To: wix-users@lists.sourceforge.net Date: Tue, 11 Oct 2011 21:01:23 + Subject: Re: [WiX-users] major upgrade from per-client to per-machine install Thanks Rob, Is there a way to detect this situation and prevent the per machine installation in such case? Thanks,Martin From: r...@robmensching.com Date: Tue, 11 Oct 2011 05:56:50 -0700 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] major upgrade from per-client to per-machine install Sadly, Windows Installer doesn't support that. On Mon, Oct 10, 2011 at 9:23 AM, Martin Kulov mar...@kulov.net wrote: Hi, (moving this to a new thread) I have an existing MSI that needs to be MajorUpgrade'd from per client to per machine installation.Right now installing the latest bits results in two versions of the program being installed side by side.This does not work for at all. How can I remove the existing per-user installation during MajorUpgrade so that the new per-machine installation can be installed instead? Thanks a lot!Martin - - All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC - - All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense
Re: [WiX-users] major upgrade from per-client to per-machine install
Thanks Rob, Is there a way to detect this situation and prevent the per machine installation in such case? Thanks,Martin From: r...@robmensching.com Date: Tue, 11 Oct 2011 05:56:50 -0700 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] major upgrade from per-client to per-machine install Sadly, Windows Installer doesn't support that. On Mon, Oct 10, 2011 at 9:23 AM, Martin Kulov mar...@kulov.net wrote: Hi, (moving this to a new thread) I have an existing MSI that needs to be MajorUpgrade'd from per client to per machine installation.Right now installing the latest bits results in two versions of the program being installed side by side.This does not work for at all. How can I remove the existing per-user installation during MajorUpgrade so that the new per-machine installation can be installed instead? Thanks a lot!Martin -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] major upgrade from per-client to per-machine install
Hi, (moving this to a new thread) I have an existing MSI that needs to be MajorUpgrade'd from per client to per machine installation.Right now installing the latest bits results in two versions of the program being installed side by side.This does not work for at all. How can I remove the existing per-user installation during MajorUpgrade so that the new per-machine installation can be installed instead? Thanks a lot!Martin -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] majorupgrade when signing and merge
I wish this was mentioned in the MajorUpgrade planning guide. I put so much efforts into planning MajorUpgrade but I totally unforseen this one. How can I uninstall the existing per user previous installations of my program now?Thanks,Martin Date: Sat, 8 Oct 2011 16:11:54 -0400 From: b...@joyofsetup.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] majorupgrade when signing and merge On 06-Oct-11 19:53, Martin Kulov wrote: files in ProgramFiles, Windows and ProgramData. Should it install per-user or per-machine mode? Per-machine; the big reason to use per-user packages is so they don't require elevation. -- sig://boB http://joyofsetup.com/ -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] majorupgrade when signing and merge
Hey John,nice to hear from you :) Yes, I did change the Product Id and Version. I used to publish 3 more upgrades already. However when I digitally signed the MSI, integrated a merge module and changed the Package InstallerVersion from 200 to 300 now the upgrade is not recognizing the old version. I keep the UpgradeCode the same. I will try adding the changes one by one and see what the problem is. Thanks,Martin From: j...@wintellect.com To: wix-users@lists.sourceforge.net; mar...@kulov.net Date: Wed, 5 Oct 2011 17:20:29 -0700 Subject: RE: [WiX-users] majorupgrade when signing and merge Hi Martin, Did you change the Product ID and the version number? Both of those have to change to be called a major upgrade. http://wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to integrate a major upgrade into your .WXS file. John Wintellect http://www.wintellect.com +1-877-968-5528 -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Wednesday, October 05, 2011 2:59 PM To: wix-users Subject: [WiX-users] majorupgrade when signing and merge Hi, I have an MSI installer built few months ago. It used to work fine during MajorUpgrade. Today I signed the MSI with code certificate and also added one Merge Module. However now my MSI file gets installed as a new product and does not upgrade the existing installation as it used to do. As usual I only changed ProductCode and CurrentVersion properties. Does digital signing or adding merge module makes the MSI look like a new product? What else could be the case? Thanks, Martin -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] majorupgrade when signing and merge
So I verified that digitally signing the MSI does NOT break MajorUpgrade process and product gets upgraded just fine.Also adding the MSM Merge module DOES break MajorUpgrade process.When I add the following two lines Merge and MergeRef I end up with two installations of my product: Directory Id=INSTALLLOCATION Name=$(var.ProductName) ... Merge Id=Microsoft_VC90_CRT_x86 Language=1033 SourceFile=Microsoft_VC90_CRT_x86.msm DiskId=1 / /Directory Feature Id=F_Complete Title=$(var.ProductName) Setup Level=1 Display=expand Absent=disallow AllowAdvertise=no ConfigurableDirectory=INSTALLLOCATION MergeRef Id=Microsoft_VC90_CRT_x86 / ... /FeatureMoving the merge module in another feature does not help either. Any ideas? Thanks,Martin From: mar...@kulov.net To: j...@wintellect.com; wix-users@lists.sourceforge.net Date: Thu, 6 Oct 2011 09:58:17 + Subject: Re: [WiX-users] majorupgrade when signing and merge Hey John,nice to hear from you :) Yes, I did change the Product Id and Version. I used to publish 3 more upgrades already. However when I digitally signed the MSI, integrated a merge module and changed the Package InstallerVersion from 200 to 300 now the upgrade is not recognizing the old version. I keep the UpgradeCode the same. I will try adding the changes one by one and see what the problem is. Thanks,Martin From: j...@wintellect.com To: wix-users@lists.sourceforge.net; mar...@kulov.net Date: Wed, 5 Oct 2011 17:20:29 -0700 Subject: RE: [WiX-users] majorupgrade when signing and merge Hi Martin, Did you change the Product ID and the version number? Both of those have to change to be called a major upgrade. http://wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to integrate a major upgrade into your .WXS file. John Wintellect http://www.wintellect.com +1-877-968-5528 -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Wednesday, October 05, 2011 2:59 PM To: wix-users Subject: [WiX-users] majorupgrade when signing and merge Hi, I have an MSI installer built few months ago. It used to work fine during MajorUpgrade. Today I signed the MSI with code certificate and also added one Merge Module. However now my MSI file gets installed as a new product and does not upgrade the existing installation as it used to do. As usual I only changed ProductCode and CurrentVersion properties. Does digital signing or adding merge module makes the MSI look like a new product? What else could be the case? Thanks, Martin -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] majorupgrade when signing and merge
So I guess you were right. Here is excerpt of the log: MSI (c) (D8:18)
[14:49:27:908]: Doing action: FindRelatedProducts
MSI (c) (D8:18) [14:49:27:908]: Note: 1: 2205 2: 3: ActionText
Action 14:49:27: FindRelatedProducts. Searching for related applications
Action start 14:49:27: FindRelatedProducts.
MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is
per-machine. Related install for product
'{AB5B1162-D4DE-4C59-BAB3-020B2323AF98}' is per-user. Skipping...
MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is
per-machine. Related install for product
'{AB5B1162-D4DE-4C59-BAB3-020B2323AF98}' is per-user. Skipping...
Action ended 14:49:27: FindRelatedProducts. Return value 1.
I do not get it why adding an MSM merge module will have any effect on the
per-machine vs per-user mode. How can I fix it back to per-machine mode?
Thanks,
Martin Kulov
Microsoft Regional Director
VS ALM MVP, MCT, INETA Speaker
www.kulov.net | (+359) 88 821 3255
From: phil.wil...@invensys.com
To: wix-users@lists.sourceforge.net
Date: Thu, 6 Oct 2011 13:17:06 -0400
Subject: Re: [WiX-users] majorupgrade when signing and merge
Two entries in Add/Remove Programs usually means you tried to upgrade a
per-system product with a per-user install, or vuice versa (all other things
being correct to do the upgrade). A verbose log will say something near the
FindRelatedProducts action.
Phil Wilson
-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net]
Sent: Thursday, October 06, 2011 3:59 AM
To: John Robbins; wix-users
Subject: Re: [WiX-users] majorupgrade when signing and merge
So I verified that digitally signing the MSI does NOT break MajorUpgrade
process and product gets upgraded just fine.Also adding the MSM Merge module
DOES break MajorUpgrade process.When I add the following two lines Merge and
MergeRef I end up with two installations of my product: Directory
Id=INSTALLLOCATION Name=$(var.ProductName)
...
Merge Id=Microsoft_VC90_CRT_x86 Language=1033
SourceFile=Microsoft_VC90_CRT_x86.msm DiskId=1 /
/Directory
Feature Id=F_Complete
Title=$(var.ProductName) Setup
Level=1
Display=expand
Absent=disallow
AllowAdvertise=no
ConfigurableDirectory=INSTALLLOCATION MergeRef
Id=Microsoft_VC90_CRT_x86 /
...
/FeatureMoving the merge module in another feature does not help either.
Any ideas? Thanks,Martin
From: mar...@kulov.net
To: j...@wintellect.com; wix-users@lists.sourceforge.net
Date: Thu, 6 Oct 2011 09:58:17 +
Subject: Re: [WiX-users] majorupgrade when signing and merge
Hey John,nice to hear from you :) Yes, I did change the Product Id and
Version. I used to publish 3 more upgrades already. However when I
digitally signed the MSI, integrated a merge module and changed the Package
InstallerVersion from 200 to 300 now the upgrade is not recognizing the old
version. I keep the UpgradeCode the same. I will try adding the changes one
by one and see what the problem is. Thanks,Martin
From: j...@wintellect.com
To: wix-users@lists.sourceforge.net; mar...@kulov.net
Date: Wed, 5 Oct 2011 17:20:29 -0700
Subject: RE: [WiX-users] majorupgrade when signing and merge
Hi Martin,
Did you change the Product ID and the version number? Both of those have
to change to be called a major upgrade.
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to
integrate a major upgrade into your .WXS file.
John
Wintellect
http://www.wintellect.com
+1-877-968-5528
-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net]
Sent: Wednesday, October 05, 2011 2:59 PM
To: wix-users
Subject: [WiX-users] majorupgrade when signing and merge
Hi,
I have an MSI installer built few months ago. It used to work fine during
MajorUpgrade.
Today I signed the MSI with code certificate and also added one Merge
Module. However now my MSI file gets installed as a new product and does
not upgrade the existing installation as it used to do. As usual I only
changed ProductCode and CurrentVersion properties.
Does digital signing or adding merge module makes the MSI look like a new
product?
What else could be the case?
Thanks,
Martin
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https
Re: [WiX-users] majorupgrade when signing and merge
indeed when I open the original MSI file with Orca ALLUSERS property is missing
(i.e. it is per-user mode).now I open the MSI file with the merge module inside
and I see ALLUSERS property is set to 1 (i.e. per-machine)there is no other
change in the WiX file so it must have been set automatically somehow when I
added the merge modulecorrection... I just opened the .msm file and the only
one property inside it is ALLUSERS=1. They must have a reason setting it up to
1. Can I override the ALLUSERS property set with the MSM file? My installer
puts files in ProgramFiles, Windows and ProgramData. Should it install per-user
or per-machine mode?
Now my MSI file is working in per-machine mode and it cannot upgrade the
existing per-user installations. What is it right way of removing existing
installations before installing the new one?Thank you so much!
Martin Kulov
Microsoft Regional Director
VS ALM MVP, MCT, INETA Speaker
www.kulov.net | (+359) 88 821 3255
From: edwin.cas...@fiserv.com
To: wix-users@lists.sourceforge.net
Date: Thu, 6 Oct 2011 18:21:37 -0400
Subject: Re: [WiX-users] majorupgrade when signing and merge
Sounds like your original package was per-user. The VC9 merge module very
likely accesses per-machine locations. That merge module must have required
that you change the package to per-machine so that it compiled successfully.
If your source control system does not show any other changes then perhaps
the per-user/per-machine setting wasn't set then WiX might have picked a
smart default based on the contents of the package. I don't know if WiX
would really do that...
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net]
Sent: Thursday, October 06, 2011 2:55 PM
To: wix-users
Subject: Re: [WiX-users] majorupgrade when signing and merge
So I guess you were right. Here is excerpt of the log: MSI (c) (D8:18)
[14:49:27:908]: Doing action: FindRelatedProducts MSI (c) (D8:18)
[14:49:27:908]: Note: 1: 2205 2: 3: ActionText Action 14:49:27:
FindRelatedProducts. Searching for related applications Action start
14:49:27:
FindRelatedProducts.
MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is per-
machine. Related install for product '{AB5B1162-D4DE-4C59-BAB3-
020B2323AF98}' is per-user. Skipping...
MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is per-
machine. Related install for product '{AB5B1162-D4DE-4C59-BAB3-
020B2323AF98}' is per-user. Skipping...
Action ended 14:49:27: FindRelatedProducts. Return value 1.
I do not get it why adding an MSM merge module will have any effect on the
per-machine vs per-user mode. How can I fix it back to per-machine mode?
Thanks,
Martin Kulov
Microsoft Regional Director
VS ALM MVP, MCT, INETA Speaker
www.kulov.net | (+359) 88 821 3255
From: phil.wil...@invensys.com
To: wix-users@lists.sourceforge.net
Date: Thu, 6 Oct 2011 13:17:06 -0400
Subject: Re: [WiX-users] majorupgrade when signing and merge
Two entries in Add/Remove Programs usually means you tried to upgrade a
per-system product with a per-user install, or vuice versa (all other things
being correct to do the upgrade). A verbose log will say something near the
FindRelatedProducts action.
Phil Wilson
-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net]
Sent: Thursday, October 06, 2011 3:59 AM
To: John Robbins; wix-users
Subject: Re: [WiX-users] majorupgrade when signing and merge
So I verified that digitally signing the MSI does NOT break MajorUpgrade
process and product gets upgraded just fine.Also adding the MSM Merge
module DOES break MajorUpgrade process.When I add the following two
lines Merge and MergeRef I end up with two installations of my product:
Directory Id=INSTALLLOCATION Name=$(var.ProductName)
...
Merge Id=Microsoft_VC90_CRT_x86 Language=1033
SourceFile=Microsoft_VC90_CRT_x86.msm DiskId=1 /
/Directory
Feature Id=F_Complete
Title=$(var.ProductName) Setup
Level=1
Display=expand
Absent=disallow
AllowAdvertise=no
ConfigurableDirectory=INSTALLLOCATION MergeRef
Id=Microsoft_VC90_CRT_x86 /
...
/FeatureMoving the merge module in another feature does not help
either. Any ideas? Thanks,Martin
From: mar...@kulov.net
To: j...@wintellect.com; wix-users@lists.sourceforge.net
Date: Thu, 6 Oct 2011 09:58:17 +
Subject: Re: [WiX-users] majorupgrade when signing and merge
Hey John,nice to hear from you :) Yes, I did change the Product Id and
Version. I used to publish 3 more upgrades already. However when I digitally
signed
[WiX-users] majorupgrade when signing and merge
Hi, I have an MSI installer built few months ago. It used to work fine during MajorUpgrade. Today I signed the MSI with code certificate and also added one Merge Module. However now my MSI file gets installed as a new product and does not upgrade the existing installation as it used to do. As usual I only changed ProductCode and CurrentVersion properties. Does digital signing or adding merge module makes the MSI look like a new product? What else could be the case? Thanks, Martin -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Another version of this product is already installed
Hi, I am using MajorUpgrade element in my wxs. When I try to install the same version of the MSI, I get the well known message: Another version of this product is already installed [Window Title] Windows Installer [Main Instruction] Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel. [OK] How can I use MajorUpgrade so that running the same version of the MSI is going to invoke Repair/Remove dialog instead? Thank you very much, Martin Kulov http://www.kulov.net -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Another version of this product is already installed
Me thinks Package Id should also be the same. In my case I tried to reinstall MSI file by setting the original Product Id and Version, and keeping Upgrade Code the same. Then I rebuild my wix project. However Package Id is set to star (*) and I get the error message below. If I reuse the same MSI file I installed the product originally from, it behaves correctly by displaying Repair/Remove options. Thanks for your help, Michael! Martin Kulov -Original Message- From: Michael Stoll [mailto:unwicht...@mistoll.de] Sent: Wednesday, June 22, 2011 9:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Another version of this product is already installed Hi, this message is displayed if you try to install a MSI with the same UpgradeCode and Version but a different ProductCode. So if you want to see the Repair/Uninstall mode you have to use a msi with the same ProductCode or maybe event the same msi, which has been used to install the product. Michael Am 22.06.2011 19:05, schrieb Martin Kulov: Hi, I am using MajorUpgrade element in my wxs. When I try to install the same version of the MSI, I get the well known message: Another version of this product is already installed [Window Title] Windows Installer [Main Instruction] Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel. [OK] How can I use MajorUpgrade so that running the same version of the MSI is going to invoke Repair/Remove dialog instead? Thank you very much, Martin Kulov http://www.kulov.net -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] logging
Hi David, I am not expert in candle and light but I believe that redirection in DOS should happen at the end of the line: RunWait($WIX_FOLDER '\candle.exe -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs myfile.txt ',$BUILD_FOLDER,@SW_MAXIMIZE) Martin Kulov -Original Message- From: David Amey [mailto:da...@creative-engine.co.uk] Sent: Wednesday, June 15, 2011 12:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] logging Hi Dave, Thank you for this link. I have been trying to implement it into my calls, but sadly it does not seem to work. I have tried the redirecting with a simple cmd call and it works fine. However I am creating an automation process using autoit, and im not sure if I would be using the redirection correctly. Autoit script: RunWait($WIX_FOLDER '\candle.exe myfile.txt -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs',$BUILD_FOLDER,@SW_MAXIMIZE) If anyone could point me in the right direction I would be incredibly grateful. Thanks! David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -Original Message- From: Dave Andersen [mailto:d.ander...@gmail.com] Sent: 14 June 2011 19:28 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] logging Something like this may help: http://blog.crankybit.com/redirecting-output-to-a-file-in-windows-batch-scri pts/ David Amey wrote: Hello All Can someone please explain how I can turn logging on during the candle and light calls, as I have errors that I need to correct. I am automating the calls, which causes the command prompt to close very quickly after the code has been run. Thanks in advance. PS thank you Tonny Erjomin for the help on language support David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/logging-tp6474 846p6475377.html Sent from the wix-users mailing list archive at Nabble.com. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] remember installed features during major upgrade
Hi, I am sure this is a commonly asked question, but I cannot find any resource explaining this. Scenario: User has installed the product and changes the default selected features to install. During major upgrade the installer fails to remember what features user has selected to install at first place and installs all features as specified by default in the MSI. Question: How should one keep user selected features between major upgrades? Thank you! Martin Kulov Microsoft Regional Director VS ALM MVP, MCT, INETA Speaker http://www.kulov.net Phone: (+359) 88 821 3255 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] remember installed features during major upgrade
Peter, I own you one! MigrateFeatures did the trick. However I need to explicitly set it to Yes, although I am doing major upgrade. UpgradeVersion Minimum=$(var.RTMVersion) IncludeMinimum=yes Maximum=$(var.CurrentVersion) IncludeMaximum=no Language=1033 Property=UPGRADEFOUND MigrateFeatures=yes / Removing MigrateFeatures attribute does not enable this behavior by default. Is this expected? Thanks a lot! Martin -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Friday, June 10, 2011 6:35 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] remember installed features during major upgrade In the upgrade installer, set UpgradeVersion/@MigrateFeatures=yes If you use MajorUpgrade, migrate features is the default. -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: 10 June 2011 16:25 To: wix-users Subject: [WiX-users] remember installed features during major upgrade Hi, I am sure this is a commonly asked question, but I cannot find any resource explaining this. Scenario: User has installed the product and changes the default selected features to install. During major upgrade the installer fails to remember what features user has selected to install at first place and installs all features as specified by default in the MSI. Question: How should one keep user selected features between major upgrades? Thank you! Martin Kulov Microsoft Regional Director VS ALM MVP, MCT, INETA Speaker http://www.kulov.net Phone: (+359) 88 821 3255 - - EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] remember installed features during major upgrade
I never expected that there is much simpler one liner solution using MajorUpdate. Somehow I missed this element. http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ Very helpful indeed. Thanks John! Martin -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Friday, June 10, 2011 9:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] remember installed features during major upgrade If you use the MajorUpgrade element then it is the default behavior. You're using the older way, so you need to specify it explicitly. -- 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: Martin Kulov [mailto:mar...@kulov.net] Sent: Friday, June 10, 2011 12:27 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] remember installed features during major upgrade Peter, I own you one! MigrateFeatures did the trick. However I need to explicitly set it to Yes, although I am doing major upgrade. UpgradeVersion Minimum=$(var.RTMVersion) IncludeMinimum=yes Maximum=$(var.CurrentVersion) IncludeMaximum=no Language=1033 Property=UPGRADEFOUND MigrateFeatures=yes / Removing MigrateFeatures attribute does not enable this behavior by default. Is this expected? Thanks a lot! Martin -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Friday, June 10, 2011 6:35 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] remember installed features during major upgrade In the upgrade installer, set UpgradeVersion/@MigrateFeatures=yes If you use MajorUpgrade, migrate features is the default. -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: 10 June 2011 16:25 To: wix-users Subject: [WiX-users] remember installed features during major upgrade Hi, I am sure this is a commonly asked question, but I cannot find any resource explaining this. Scenario: User has installed the product and changes the default selected features to install. During major upgrade the installer fails to remember what features user has selected to install at first place and installs all features as specified by default in the MSI. Question: How should one keep user selected features between major upgrades? Thank you! Martin Kulov Microsoft Regional Director VS ALM MVP, MCT, INETA Speaker http://www.kulov.net Phone: (+359) 88 821 3255 - - EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-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
[WiX-users] moving component to another feature
Hi,
I have one component that I need to move from one feature to another.
Should I change the component GUID in order to prevent orphaned files?
Directory Id=INSTALLLOCATION Name=$(var.ProductName)
Component Id=Comp1 Guid={SOME-GUID}
File Id=FL1 KeyPath=yes Source=command.bat /
/Component
/Directory
Feature Id='F1'
Title=my feature
Level=110
AllowAdvertise=no
ConfigurableDirectory=INSTALLLOCATION
ComponentRef Id=Comp1 /
/Feature
Thanks,
Martin Kulov
http://www.kulov.net
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] deferred task with elevated impersonation
Thanks Bob! Running from elevated command prompt did it. Martin -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Monday, May 30, 2011 6:59 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] deferred task with elevated impersonation On 28-May-11 06:36, Martin Kulov wrote: How can I execute deferred task with elevated privileges under user's running the installer credentials? MSI doesn't support that except by running the entire .msi from an elevated process. -- sig://boB http://joyofsetup.com/ -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] orphaned desktop shortcut
Blair,
Can you please give more guidance/tips here?
Thanks!
Martin
-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net]
Sent: Saturday, May 28, 2011 4:20 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] orphaned desktop shortcut
Thanks Blair,
How should one manage changes in non-keypath components?
Martin
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Saturday, May 28, 2011 3:43 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] orphaned desktop shortcut
That is a consequence of changing non-keypath resources in a component. A
component's identity consists of its keypath, not its entire composition.
You could try using DeleteFile/ to remove the orphaned shortcut.
-Blair
From: mar...@kulov.net
To: wix-users@lists.sourceforge.net
Date: Sat, 28 May 2011 00:25:09 +0300
Subject: [WiX-users] orphaned desktop shortcut
Hi,
I am creating desktop shortcut inside a Component.
After installing the product, I renamed the shortcut and performed
major upgrade.
The upgrade left me with two shortcuts (the original one and the new
renamed one). After uninstalling the product, the original shortcut
was left orphaned. I did not change the component guid as the shortcut
is not keypath.
Here is excerpt of my code:
Directory Id=ProgramMenuFolder Name=Programs
Directory Id=ProgramMenuDir Name=$(var.ProductName)
Component Id=Comp_ProgramMenuDir
Guid={66C429C9-477D-4C48-8B64-0A480F7AB472}
RemoveFolder Id='ProgramMenuDir' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\$(var.Manufacturer)\$(var.ProductName)' Type='string'
Value=''
KeyPath='yes' /
Shortcut Id='desktopMyWin'
Directory='DesktopFolder'
Name='$(var.ProductName) Command Prompt'
WorkingDirectory='MyFolder'
Icon='MyIcon.ico'
Target='[%ComSpec]'
Arguments='[SHELLARGS]'
Advertise='no' /
/Component
/Directory
/Directory
Can you please help?
Thank you!
Martin Kulov
Microsoft Regional Director
VS ALM MVP, MCT, INETA Speaker
http://www.kulov.net
Phone: (+359) 88 821 3255
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, you
get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, you get
blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] deferred task with elevated impersonation
Hi, I am running a CAQuietExec deferred task as shown below. When executed , my command fails with Access Denied error. I can see that the user executing my command is SYSTEM. I need to execute my command under user credentials. Changing Impersonate to yes doesn't help as the task is no longer elevated. How can I execute deferred task with elevated privileges under user's running the installer credentials? CustomAction Id=CA_Config Execute=deferred Impersonate=no BinaryKey=WixCA DllEntry=CAQuietExec Return='ignore' / Thank you, Martin Kulov Microsoft Regional Director VS ALM MVP, MCT, INETA Speaker http://www.kulov.net Phone: (+359) 88 821 3255 -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] orphaned desktop shortcut
Hi,
I am creating desktop shortcut inside a Component.
After installing the product, I renamed the shortcut and performed major
upgrade.
The upgrade left me with two shortcuts (the original one and the new renamed
one). After uninstalling the product, the original shortcut was left
orphaned. I did not change the component guid as the shortcut is not
keypath.
Here is excerpt of my code:
Directory Id=ProgramMenuFolder Name=Programs
Directory Id=ProgramMenuDir Name=$(var.ProductName)
Component Id=Comp_ProgramMenuDir
Guid={66C429C9-477D-4C48-8B64-0A480F7AB472}
RemoveFolder Id='ProgramMenuDir' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\$(var.Manufacturer)\$(var.ProductName)' Type='string' Value=''
KeyPath='yes' /
Shortcut Id='desktopMyWin'
Directory='DesktopFolder'
Name='$(var.ProductName) Command Prompt'
WorkingDirectory='MyFolder'
Icon='MyIcon.ico'
Target='[%ComSpec]'
Arguments='[SHELLARGS]'
Advertise='no' /
/Component
/Directory
/Directory
Can you please help?
Thank you!
Martin Kulov
Microsoft Regional Director
VS ALM MVP, MCT, INETA Speaker
http://www.kulov.net
Phone: (+359) 88 821 3255
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] orphaned desktop shortcut
Thanks Blair,
How should one manage changes in non-keypath components?
Martin
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Saturday, May 28, 2011 3:43 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] orphaned desktop shortcut
That is a consequence of changing non-keypath resources in a component. A
component's identity consists of its keypath, not its entire composition.
You could try using DeleteFile/ to remove the orphaned shortcut.
-Blair
From: mar...@kulov.net
To: wix-users@lists.sourceforge.net
Date: Sat, 28 May 2011 00:25:09 +0300
Subject: [WiX-users] orphaned desktop shortcut
Hi,
I am creating desktop shortcut inside a Component.
After installing the product, I renamed the shortcut and performed
major upgrade.
The upgrade left me with two shortcuts (the original one and the new
renamed one). After uninstalling the product, the original shortcut
was left orphaned. I did not change the component guid as the shortcut
is not keypath.
Here is excerpt of my code:
Directory Id=ProgramMenuFolder Name=Programs
Directory Id=ProgramMenuDir Name=$(var.ProductName)
Component Id=Comp_ProgramMenuDir
Guid={66C429C9-477D-4C48-8B64-0A480F7AB472}
RemoveFolder Id='ProgramMenuDir' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\$(var.Manufacturer)\$(var.ProductName)' Type='string'
Value=''
KeyPath='yes' /
Shortcut Id='desktopMyWin'
Directory='DesktopFolder'
Name='$(var.ProductName) Command Prompt'
WorkingDirectory='MyFolder'
Icon='MyIcon.ico'
Target='[%ComSpec]'
Arguments='[SHELLARGS]'
Advertise='no' /
/Component
/Directory
/Directory
Can you please help?
Thank you!
Martin Kulov
Microsoft Regional Director
VS ALM MVP, MCT, INETA Speaker
http://www.kulov.net
Phone: (+359) 88 821 3255
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, you
get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, you get
blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] dependent features
Hi Peter, Thanks for the reference. I did not know this Windows feature. However I am having hard time finding out how it actually works. I create a subkey called myapp.exe under KEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\App Paths. Then I put full path to myapp.exe in the Default REG_SZ value. I open a new Command Prompt and try to run myapp.exe. I've got an error that Windows cannot find myapp.exe. Is it supposed to work like this? Thanks, Martin -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, May 10, 2011 11:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] dependent features App Paths would be a neat way to solve this, if they meet all your requirements. The registration lives in components that you can add to the features. http://msdn.microsoft.com/en-us/library/ee872121%28v=vs.85%29.aspx#reg_app -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: 09 May 2011 22:41 To: wix-users Subject: [WiX-users] dependent features Hi all, I would like to set environment variable PATH based on other features that user has selected to install. PATH should set only the paths for selected features. Additionally user must turn on and off PATH registration by choosing to install feature called Register Environment Variables. Based on the article below I found that it is not possible to have a component condition based on feature state: http://www.joyofsetup.com/2008/04/09/feature-states-in-component-conditions/ I spent my day looking for a solution, so any ideas would be extremely helpful. Thanks, Martin Kulov http://www.kulov.net - - WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] dependent features
For the archive: I implemented this as two separate Components (different GUIDs) having Environment element. Both Environment elements use value from same property PATHADD. However PATHADD is set using CustomAction Property having condition to set value to the property only when both features are being installed (or one is being installed and the other one is already installed). Also PATHADD is being set when feature is uninstalled, so that proper uninstallation will take place when either one of the features get removed. As a result I am able to set PATH environment variables only when both Feature1 and Register Env Variables feature are installed. If either one of them gets removed, PATH value is also removed. I did not have to save PATHADD property in registry or something else, as it is constructed from INSTALLLOCATION property. I am not sure how but it looks like it is preserved during install/uninstall process. Any info on this one would be very helpful. Thank you, Martin -Original Message- From: Michael Osmond [mailto:mosm...@baytech.com.au] Sent: Tuesday, May 10, 2011 4:31 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] dependent features Not certain, but try saving the Path add string to registry and read it back in on Uninstall. Also if someone adds a Feature through maintenance mode, you can append to the path string. Your biggest issue would be if someone selectively removes a feature. Michael -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Tuesday, 10 May 2011 11:14 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] dependent features Michael, Any tips on how to implement compensating action on uninstall? Should I preserve the property in xml file or registry? Any other implementation? Martin -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Tuesday, May 10, 2011 3:32 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] dependent features Hi Michael, That was something I was playing with. However your solution just nailed it! One comment for the history - one should use public property like PATHADD instead of PathAdd to make sure property is transferred between user and service mode. Thanks a lot! Martin From: mosm...@baytech.com.au To: wix-users@lists.sourceforge.net Date: Tue, 10 May 2011 08:04:59 +1000 Subject: Re: [WiX-users] dependent features Hi Martin You could build up a single property with the PATH entry you wish to add using a series of Type 51 Custom Actions. Each would add the path option for a feature and be conditioned by the feature state. You then have a single component (linked to you Register Environment Variables feature) which actually applies the values. Pseudo code would be something like CustomAction Id=Feature1.AddToPath Property=PathAdd Value=[PathAdd];Feature1Path / CustomAction Id=Feature2.AddToPath Property=PathAdd Value=[PathAdd];Feature2Path / InstallExecuteSequence Custom Action=Feature1.AddToPath After=CostFinalizeFeature1 = 3/CustomAction Custom Action=Feature2.AddToPath After= Feature1.AddToPathFeature2 = 3/CustomAction /InstallExecuteSequence Component Id= Register Environment Variables Component Add [PathAdd] to registry /Component Regards Michael -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Tuesday, 10 May 2011 7:41 AM To: wix-users Subject: [WiX-users] dependent features Hi all, I would like to set environment variable PATH based on other features that user has selected to install. PATH should set only the paths for selected features. Additionally user must turn on and off PATH registration by choosing to install feature called Register Environment Variables. Based on the article below I found that it is not possible to have a component condition based on feature state: http://www.joyofsetup.com/2008/04/09/feature-states-in-component-condi tions/ I spent my day looking for a solution, so any ideas would be extremely helpful. Thanks, Martin Kulov http://www.kulov.net -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today
[WiX-users] dependent features
Hi all, I would like to set environment variable PATH based on other features that user has selected to install. PATH should set only the paths for selected features. Additionally user must turn on and off PATH registration by choosing to install feature called Register Environment Variables. Based on the article below I found that it is not possible to have a component condition based on feature state: http://www.joyofsetup.com/2008/04/09/feature-states-in-component-conditions/ I spent my day looking for a solution, so any ideas would be extremely helpful. Thanks, Martin Kulov http://www.kulov.net -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] dependent features
Hi Michael, That was something I was playing with. However your solution just nailed it! One comment for the history - one should use public property like PATHADD instead of PathAdd to make sure property is transferred between user and service mode. Thanks a lot! Martin From: mosm...@baytech.com.au To: wix-users@lists.sourceforge.net Date: Tue, 10 May 2011 08:04:59 +1000 Subject: Re: [WiX-users] dependent features Hi Martin You could build up a single property with the PATH entry you wish to add using a series of Type 51 Custom Actions. Each would add the path option for a feature and be conditioned by the feature state. You then have a single component (linked to you Register Environment Variables feature) which actually applies the values. Pseudo code would be something like CustomAction Id=Feature1.AddToPath Property=PathAdd Value=[PathAdd];Feature1Path / CustomAction Id=Feature2.AddToPath Property=PathAdd Value=[PathAdd];Feature2Path / InstallExecuteSequence Custom Action=Feature1.AddToPath After=CostFinalizeFeature1 = 3/CustomAction Custom Action=Feature2.AddToPath After= Feature1.AddToPathFeature2 = 3/CustomAction /InstallExecuteSequence Component Id= Register Environment Variables Component Add [PathAdd] to registry /Component Regards Michael -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Tuesday, 10 May 2011 7:41 AM To: wix-users Subject: [WiX-users] dependent features Hi all, I would like to set environment variable PATH based on other features that user has selected to install. PATH should set only the paths for selected features. Additionally user must turn on and off PATH registration by choosing to install feature called Register Environment Variables. Based on the article below I found that it is not possible to have a component condition based on feature state: http://www.joyofsetup.com/2008/04/09/feature-states-in-component-conditions/ I spent my day looking for a solution, so any ideas would be extremely helpful. Thanks, Martin Kulov http://www.kulov.net -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] dependent features
Michael, Any tips on how to implement compensating action on uninstall? Should I preserve the property in xml file or registry? Any other implementation? Martin -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Tuesday, May 10, 2011 3:32 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] dependent features Hi Michael, That was something I was playing with. However your solution just nailed it! One comment for the history - one should use public property like PATHADD instead of PathAdd to make sure property is transferred between user and service mode. Thanks a lot! Martin From: mosm...@baytech.com.au To: wix-users@lists.sourceforge.net Date: Tue, 10 May 2011 08:04:59 +1000 Subject: Re: [WiX-users] dependent features Hi Martin You could build up a single property with the PATH entry you wish to add using a series of Type 51 Custom Actions. Each would add the path option for a feature and be conditioned by the feature state. You then have a single component (linked to you Register Environment Variables feature) which actually applies the values. Pseudo code would be something like CustomAction Id=Feature1.AddToPath Property=PathAdd Value=[PathAdd];Feature1Path / CustomAction Id=Feature2.AddToPath Property=PathAdd Value=[PathAdd];Feature2Path / InstallExecuteSequence Custom Action=Feature1.AddToPath After=CostFinalizeFeature1 = 3/CustomAction Custom Action=Feature2.AddToPath After= Feature1.AddToPathFeature2 = 3/CustomAction /InstallExecuteSequence Component Id= Register Environment Variables Component Add [PathAdd] to registry /Component Regards Michael -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Tuesday, 10 May 2011 7:41 AM To: wix-users Subject: [WiX-users] dependent features Hi all, I would like to set environment variable PATH based on other features that user has selected to install. PATH should set only the paths for selected features. Additionally user must turn on and off PATH registration by choosing to install feature called Register Environment Variables. Based on the article below I found that it is not possible to have a component condition based on feature state: http://www.joyofsetup.com/2008/04/09/feature-states-in-component-condi tions/ I spent my day looking for a solution, so any ideas would be extremely helpful. Thanks, Martin Kulov http://www.kulov.net -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
