[WiX-users] Why is WiX UI executed after CostFinalize?
I have suffered form the standard problem that many people on this mailing list hit where conditions on features apparently don't work because the UI is executed after the CostFinalize action when these are applied. Why is the UI run after Cost Finalize rather than before it? If the UI were run earlier then Feature conditions would work in the obvious manner but I assume other problems would occur. Does anyone know what those problems are likely to be? Are they less troublesome than the problems caused by the existing order of execution? Thanks in advance -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Why-is-WiX-UI-executed-after-CostFinalize-tp6047911p6047911.html Sent from the wix-users mailing list archive at Nabble.com. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] write to IniFile
I'm trying to write to an iniFile. How do I tell it which folder the file is in? Currently it seems to insist that it is in the \Windows folder. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: Planning: package customization
Actually Bob Arnson was right.
I have the following code works:
1) In Bundle.wxs:
Variable Name=db_name Value=old_db_name/
Chain
MsiPackage Id=SomeMsiId SourceFile=some.msi
MsiProperty Name=DB_NAME Value=db_name/
/MsiPackage
/Chain
2) In BA managed code:
MyBootstrapperApplication.Bootstrapper.Engine.StringVariables[db_name] =
new_db_name;
Now some.msi will be launched something like this: msiexec.msi /I some.msi
DB_NAME=new_db_name
The tip is: Value in MsiProperty values EXPRESSION that can contains
references to Burn variables (like db_name in my example)
From: Dan Vasilov d...@rms.ro
Subject: Re: [WiX-users] Burn: Planning: package customization
To: 'General discussion for Windows Installer XML toolset.'
wix-users@lists.sourceforge.net
Message-ID: 005301cbd195$cdd65860$69830920$@ro
Content-Type: text/plain; charset=us-ascii
You can implement the bootstrapper to launch the .msi package using
the command line msiexec /I {package.msi} PROPERTY1=value1 PROPERTY2=value2.
However, if you do this, you have to manually manage all specific
scenarios (upgrade, uninstall, patch, etc).
A better solution is to encapsulate the code to retrieve specific
information in custom actions and drop the bootstrapper altogether.
Dan
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.
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat: the ID of a directory with numeric name
Hi, I guess this question is for me rather than for Palbinder. I am running heat 3.0.5419.0. And I do use -suid (on purpose). Anyway, this is not critical, I was just wondering if there was a good explanation for the ID change from Directory1234 to _1234, but I can live with it. Thanks a lot, Sam --- Date: Thu, 17 Feb 2011 08:59:39 -0800 From: Brian Rogers rogers.br...@gmail.com Subject: Re: [WiX-users] heat: the ID of a directory with numeric name To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Message-ID: AANLkTinsPkGfV=P=j6x+m2-zg0olr7_nxhugukqq8...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hey Palbinder, Which version of heat.exe are you using? As long as you aren't using -suid you should be ok. Thanks, Brian Rogers Intelligence removes complexity. - Me http://blogs.msdn.com/icumove On Thu, Feb 17, 2011 at 2:10 AM, samuel.feren...@barclayscapital.comwrote: Hi Palbinder, (group), thanks for your response. As per the link you said, an ID of 1234 is *not* acceptable (every identifier must begin with either a letter or an underscore), which is why I think heat does some magic to avoid that ID for a directory called 1234. It seems that in one case heat generates the ID Directory1234 and in another _1234, and I'm wondering if this is something that one can control in heat (or if, perhaps, this is due to different versions of heat...) Thanks, Sam -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 11 February 2011 17:32 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] heat: the ID of a directory with numeric name Directory ID's can be anything you like as long as they're valid identifiers (see http://msdn.microsoft.com/en-gb/library/aa369212.aspx) since they go directly into the Directory table. They don't need to reflect the actual name of the directory. Just rename it after harvesting. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: samuel.feren...@barclayscapital.com [mailto:samuel.feren...@barclayscapital.com] Sent: 11 February 2011 14:05 To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat: the ID of a directory with numeric name Hi, I am harvesting (heat dir) a directory structure like this: foo + bar + 1234 + a.a + b.b The output is as follows: DirectoryRef Id=TARGETDIR Directory Id=foo Name=foo Directory Id=bar Name=bar Directory Id=_1234 Name=1234 I am wondering about the Id _1234. I suppose the Id cannot be purely numeric, so the underscore is prepended. However, I'm trying to mimic another MSI package, and that one has the Id of Directory1234: DirectoryRef Id=TARGETDIR Directory Id=foo Name=foo Directory Id=bar Name=bar Directory Id=Directory1234 Name=1234 How can that be achieved? Thanks, Sam ___ This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group. ___ -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
Re: [WiX-users] heat: the ID of a directory with numeric name
You can use the -t:xsl (transform harvested output with XSL file) parameter to use a XSL-transform. A sample XSLT can be found here: http://www.wixwiki.com/index.php?title=Heat or search this mailing list e.g. at http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ for some samples. Additionally XMLspy has a good debugger to track the modifications an XSLT is doing on a XML file. Regards Tobias 2011/2/21 samuel.feren...@barclayscapital.com: Hi, I guess this question is for me rather than for Palbinder. I am running heat 3.0.5419.0. And I do use -suid (on purpose). Anyway, this is not critical, I was just wondering if there was a good explanation for the ID change from Directory1234 to _1234, but I can live with it. Thanks a lot, Sam --- Date: Thu, 17 Feb 2011 08:59:39 -0800 From: Brian Rogers rogers.br...@gmail.com Subject: Re: [WiX-users] heat: the ID of a directory with numeric name To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Message-ID: AANLkTinsPkGfV=P=j6x+m2-zg0olr7_nxhugukqq8...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hey Palbinder, Which version of heat.exe are you using? As long as you aren't using -suid you should be ok. Thanks, Brian Rogers Intelligence removes complexity. - Me http://blogs.msdn.com/icumove On Thu, Feb 17, 2011 at 2:10 AM, samuel.feren...@barclayscapital.comwrote: Hi Palbinder, (group), thanks for your response. As per the link you said, an ID of 1234 is *not* acceptable (every identifier must begin with either a letter or an underscore), which is why I think heat does some magic to avoid that ID for a directory called 1234. It seems that in one case heat generates the ID Directory1234 and in another _1234, and I'm wondering if this is something that one can control in heat (or if, perhaps, this is due to different versions of heat...) Thanks, Sam -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 11 February 2011 17:32 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] heat: the ID of a directory with numeric name Directory ID's can be anything you like as long as they're valid identifiers (see http://msdn.microsoft.com/en-gb/library/aa369212.aspx) since they go directly into the Directory table. They don't need to reflect the actual name of the directory. Just rename it after harvesting. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: samuel.feren...@barclayscapital.com [mailto:samuel.feren...@barclayscapital.com] Sent: 11 February 2011 14:05 To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat: the ID of a directory with numeric name Hi, I am harvesting (heat dir) a directory structure like this: foo + bar + 1234 + a.a + b.b The output is as follows: DirectoryRef Id=TARGETDIR Directory Id=foo Name=foo Directory Id=bar Name=bar Directory Id=_1234 Name=1234 I am wondering about the Id _1234. I suppose the Id cannot be purely numeric, so the underscore is prepended. However, I'm trying to mimic another MSI package, and that one has the Id of Directory1234: DirectoryRef Id=TARGETDIR Directory Id=foo Name=foo Directory Id=bar Name=bar Directory Id=Directory1234 Name=1234 How can that be achieved? Thanks, Sam ___ This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other
Re: [WiX-users] Enabling/disabling features by script
Found out how it works: IN a jscript simply do Session.Property(ADDLOCAL) = ALL; Session.Property(REMOVE) = FeatureName; That's all! -Original Message- From: Eschenbacher, Frank [mailto:frank.eschenbac...@voltdelta.net] Sent: Thursday, February 17, 2011 8:05 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Enabling/disabling features by script Hi all, does anyone know how to enable or disable a feature in a script? Cheers Frank Go Green - Please consider the environment before printing this email /PREhtmlp style=color: black; font-family: Arial; font-size: 8pt Volt Delta International GmbH, Landsberger Str. 110, D-80339 Muenchen br / Sitz: Muenchen, Amtsgericht Muenchen, HRB 156693, VAT-ID DE814437634 br / Managing Directors (Geschaeftsfuehrer): Noel Hughes, Hans Pokorny, Yusuf Bulan /p /html -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Volt Delta International GmbH, Landsberger Str. 110, D-80339 Muenchen Sitz: Muenchen, Amtsgericht Muenchen, HRB 156693, VAT-ID DE814437634 Managing Directors (Geschaeftsfuehrer): Noel Hughes, Hans Pokorny, Yusuf Bulan -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patching Using Purely Wix
Peter, Thanks you for your reply. This does seem very promising; I'll let you know how we get on with it. Cheers, Liam -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 17 February 2011 10:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patching Using Purely Wix Would creating a pure Wix patch from administrative installations work for you ? It's what we do here. This gives you an idea of the process. http://blogs.msdn.com/b/pmarcu/archive/2008/05/30/patching-something-you-did n t-build-with-wix-using-wix-.aspx -Original Message- From: Liam Flanagan [mailto:l...@dyalog.com] Sent: 16 February 2011 12:46 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Patching Using Purely Wix Hello All, I've been wondering if it's possible to create minor patches using the purely wix method, however only using the baseline and QFE MSI packages instead of requiring the original source files and structure that the MSIs were built from. I want have the benefits of purely wix patching (i.e. referencing wix components etc) however not the complexity of having build output snapshots that have a large quantities of files and file structures, instead simply the released MSIs. The table in this msdn blog ( http://blogs.msdn.com/b/heaths/archive/2010/08/24/comparison-of-patchwiz-and -wix-v3-patch-build.aspx ) implies that these should be possible; although I guess not all at the same time. (CF: ticks in the Ignore certain other resource types to be upgraded by the patch (ex: registry values, components, etc.) and Can automatically extract compressed files when creating transforms. Boxes) A little background into what I've tried so far: . Using the wixpdb files with torch to create the transform between the two versions appears to require the original msi build structure when creating the patch . Using torch on the msi files as standard appears to create a binary mst file, I presume this is for use with PatchWiz as Wix tools don't seem to like this at all . If whilst using torch on the msi files you specify you want an xml output (wixout) you appear to get a file very similar to that of the output when using torch on the wixpdb files, however you appear to lose all information about wix structures (wix components/component groups etc). Therefore if I try to specify them in the patch.wxs, pyro doesn't understand what differences you're actually trying to bring through in the patch. Furthermore on this, this fairly dated blog post ( http://blogs.msdn.com/b/pmarcu/archive/2007/04/27/building-a-patch-using-wix -v3-0.aspx ) implies that when creating the original msi files creating an interim wixmsi and using light to convert that into an MSI rather than just lighting the wixobj may change the game a bit; however I couldn't get this to work. The produced MSI files whilst having different md5sums appeared identical in Orca and furthermore produced identical wixout files via torch. Is what I'm hoping for achievable? Thanks, Liam - - The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ 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. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance.
Re: [WiX-users] write to IniFile
Yep, annoying, eh? The MSI SDK documents that behavior. Want to contribute a custom action that does better? On Mon, Feb 21, 2011 at 1:04 AM, Michael Tissington michael_tissing...@ciqual.com wrote: I'm trying to write to an iniFile. How do I tell it which folder the file is in? Currently it seems to insist that it is in the \Windows folder. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] write to IniFile
Actually I have got it to work just great. It was a spelling mistake on my part. Component Id=Data Guid=PUT-GUID-HERE CreateFolder Permission User=!(loc.EveryoneGroup) GenericAll=yes/ /CreateFolder CopyFile Id=ini FileId=myini / IniFile Id=ServerAddress Directory=ApplicationNameData Name=myfile.ini Section=ConnectionObserver Key=ServerAddress Value=[SERVERADDRESS] Action=addLine/ IniFile Id=GroupID Directory=ApplicationNameData Name=ciquald.ini Section=PopupQuestion Key=GroupID Value=[GROUPID] Action=addLine/ RemoveFile Id=PurgeDataFolder Name=*.* On=uninstall / /Component -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 21 February 2011 15:03 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] write to IniFile Yep, annoying, eh? The MSI SDK documents that behavior. Want to contribute a custom action that does better? On Mon, Feb 21, 2011 at 1:04 AM, Michael Tissington michael_tissing...@ciqual.com wrote: I'm trying to write to an iniFile. How do I tell it which folder the file is in? Currently it seems to insist that it is in the \Windows folder. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] write to IniFile
http://msdn.microsoft.com/en-us/library/aa369282(VS.85).aspx DirProperty Name of a property having a value that resolves to the full path of the folder containing the .ini file. The property can be the name of a directory in the Directory table, a property set by the AppSearch table, or any other property that represents a full path. If this field is left blank, the .ini file is created in the folder having the full path specified by the WindowsFolder property. Unless I'm missing something obvious, shouldn't it be as simple as specifying a value for DirProperty? We do this from WiX in our product with no problems so far... don't really see why a custom action would be needed... -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Monday, February 21, 2011 15:03 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] write to IniFile Yep, annoying, eh? The MSI SDK documents that behavior. Want to contribute a custom action that does better? On Mon, Feb 21, 2011 at 1:04 AM, Michael Tissington michael_tissing...@ciqual.com wrote: I'm trying to write to an iniFile. How do I tell it which folder the file is in? Currently it seems to insist that it is in the \Windows folder. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Why is WiX UI executed after CostFinalize?
http://msdn.microsoft.com/en-us/library/aa368048(v=vs.85).aspx CostFinalize must be run before UI is displayed to allow Features to be selected or Directories to be changed, which most installer UIs allow users to do. If you are changing properties that affect component/feature conditioning in your UI, you can run CostFinalize again to have the installation states reevaluated. You just need to execute the CostFinalize action from a DoAction control event after the appropriate property values have been set. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Why-is-WiX-UI-executed-after-CostFinalize-tp6047911p6049379.html Sent from the wix-users mailing list archive at Nabble.com. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Running a custom action with elevated privileges
The system account is irrelevant here. What matters is the list of rights that the msiexec process is running with, and it does not have all possible rights enabled all of the time. I think you've already discovered that, so I don't know what to advise. I forget where this is documented, but that code (and therefore your custom action) is running with a limited list of rights (something that started on MSI 4.0) that does not include the one required to terminate processes. Phil Wilson -Original Message- From: Jeff Wisgo [mailto:locksl...@gmail.com] Sent: Sunday, February 20, 2011 3:32 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Running a custom action with elevated privileges Umesh, Thanks for responding to my question. I am using OpenProcess(PROCESS_TERMINATE, ...). When I execute the same exact code from a system account with elevated privileges using PSEXEC, it works, so I know there is something wrong with the privileges when my code runs as a Custom Action. I also have verified this by looking at the privileges with Process Explorer. Any other ideas? Thanks, Jeff On Sat, Feb 19, 2011 at 12:56 AM, Umeshj umesh_jogle...@hotmail.com wrote: What access level are you using for OpenProcess() ? A simple PROCESS_TERMINATE is sufficient. If you are using PROCESS_ALL_ACCESS it will fail. I had experienced the same problems and after changing the dwDesiredAccess param it worked well. Umesh -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Running-a-custom-action-with-elevated-privileges-tp6041158p6042577.html Sent from the wix-users mailing list archive at Nabble.com. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ 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/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. 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). -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to change the Windows Integrity level in Vista/Win7 when launching the application
Thanks Rob for your reply. Honestly, I'm not sure when the custom action is scheduled because I took the example(How To: Run the Installed Application After Setup) from Wix.chm. Here's our code: Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT Value=!(loc.LaunchAppString) $(var.ApplicationName) / Property Id=WixShellExecTarget Value=[INSTALLLOCATION]$(var.ExeFile) / CustomAction Id=LaunchApplication BinaryKey=WixCA DllEntry=WixShellExec Impersonate=no / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchApplication WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed /Publish As you can see, it's almost identical to the original example code in Wix.chm. Anyways, I also run the installer and checked the log. Here's some log: MSI (c) (B8:D4) [11:44:33:697]: Decrementing counter to disable shutdown. If counter = 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (B8:D4) [11:44:33:697]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'. Action ended 11:44:33: ExecuteAction. Return value 1. MSI (c) (B8:D4) [11:44:33:697]: Doing action: ExitDialog Action 11:44:33: ExitDialog. Action start 11:44:33: ExitDialog. Action 11:44:33: ExitDialog. Dialog created MSI (c) (B8:DC) [11:44:35:785]: Doing action: LaunchApplication Action 11:44:35: LaunchApplication. Action start 11:44:35: LaunchApplication. MSI (c) (B8:EC) [11:44:35:787]: Invoking remote custom action. DLL: C:\Users\UserA\AppData\Local\Temp\MSI8A32.tmp, Entrypoint: WixShellExec Action ended 11:44:36: LaunchApplication. Return value 1. Action ended 11:44:36: ExitDialog. Return value 1. Action ended 11:44:36: INSTALL. Return value 1. MSI (c) (B8:D4) [11:44:36:124]: Destroying RemoteAPI object. MSI (c) (B8:48) [11:44:36:124]: Custom Action Manager thread ending. So the question now is: is there a way to launch the application by giving the same Integrity Level as we start it from the system Start menu? Thanks a lot. From: Rob Mensching r...@robmensching.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Sat, February 19, 2011 9:26:54 AM Subject: Re: [WiX-users] How to change the Windows Integrity level in Vista/Win7 when launching the application When is your custom action scheduled? On Fri, Feb 18, 2011 at 3:17 PM, little.forest little.for...@ymail.comwrote: We found a problem in Vista/Win7: If we launch the application from the installer for the fresh installation, the Integrity level is empty. The process is on the same level as explorer.exe. If we start the application from Start menu after the installation, the Integrity level is Medium(just like other applications). And the process is under explorer.exe. The question is, how to launch the application from installer to make it have Medium Integrity level. By the way, by using Process Explorer from SystemInternals and turning on the Integrity field, the Integrity level field will show up. The reason we ask this is because: we have a bug which seems related to this Integrity Level thing. If the app is started from the Start menu, things are fine. If the app is launched from the installer for the 1st time installation, some functionalities don't work. I tried to set the 'Impersonate' field to be 'no'. But it doesn't help. Here's our launch app code: Property Id=WixShellExecTarget Value=[INSTALLLOCATION]$(var.ExeFile) / CustomAction Id=LaunchApplication BinaryKey=WixCA DllEntry=WixShellExec Impersonate=no / Thanks in advance. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Index, Search Analyze Logs and other IT data in Real-Time with Splunk Collect, index and harness all the fast moving IT data generated by your
[WiX-users] MSBuild batching - Disabling incremental clean of MSIs only
Hi I rely on batching to generate multiple sets of MSIs from the same wixproj files. The files are generated to the same output location, but are different based on properities I pass to the wixproj files that control thigns like the MSI name, etc. I'd typically invoke the project as follows MSBuild Project=Foo.sln Targets=Clean;X;Y;Z Properties=Bar=%(SomeItem.Identity)/ With WiX 3.5.1623 this worked. The Clean target resulted in deleting the wixobj file, but not the MSIs. After upgrading to 3.5.2519, I noticed that the incremental clean kicks in and deletes the MSIs from an earlier iteration in the batch, thus breaking my build. My msbuild file's Clean target removes the necessary MSIs, so I just need to delete all the wixobj files when building the clean target of the WiX solution. Even if I skip Clean and just call the project targets in the solution, the incremental clean still deletes the MSI from the previous build. Was there a fix made between 3.5.1623 and 3.5.2519 that could explain the change in behavior or is there another work-around for this? The closest changeset I could find that seemed related was http://sourceforge.net/tracker/?func=detailaid=3062699group_id=105970atid=642714 Did I perhaps rely on a bug? Thanks, Jacques -- Index, Search Analyze Logs and other IT data in Real-Time with Splunk Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. Free Software Download: http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Problem with RemoveExistingProducts action
I have upgrade scenario for my system from 2.0 version to 2.1 version. I
have file for example aaa.xml in 2.1 version and no such file in 2.0
version. It lies in independent component i feature Afeature (it was in 2.0
also). During install there are no problems: file installs to the right
location. But during upgrade from 2.0 version it copies and then deleted.
It seems that RemoveExistingProducts deletes it during uninstall of older
2.0 product. It planned after InstallFinalize action (the most right place
as I understand).
Due to the log Installer unpublish features and the delete files...
MSI (s) (DC:B8) [11:54:05:148]: Executing op:
FileRemove(,FileName=aaa.xml,,ComponentId={369A88EA-F2DD-4124-9560-13E5694E2EEB})
RemoveFiles: File: aaa.xml, folder: C:\Mag\
I dont understand - what happened? Why it deletes files? May be I didnt
configured installer correctly? But how?
--
Index, Search Analyze Logs and other IT data in Real-Time with Splunk
Collect, index and harness all the fast moving IT data generated by your
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights.
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
