CreateFolder does not delete folders. I do believe that Permission element
will explictily set the ACLs on the directory though.
On Sat, Oct 24, 2009 at 5:00 PM, Balu Swaminathan wrote:
>
> Hello All:
>
>
>
> Is it possible to author a wix file which can grant permission to a folder
> (not create
If you mark your custom action as a 64-bit action it should run in a 64-bit
process. I haven't tried it with DTF since I write all my custom actions in
C/C++.
On Sat, Oct 24, 2009 at 7:37 PM, Dave Kolb wrote:
> Good information Blair and thanks. I did not know about the EventSource
> element but
Thanks John!
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Saturday, October 24, 2009 11:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do I add both a HKLM and a HKCU key
We do this and it works for us (Same situation).
Add a reference to the util extension, and add it to your namespace definitions
http://schemas.microsoft.com/wix/2006/wi";
xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension";
xmlns:util="http://schemas.microsoft.com/wix/UtilExten
Good information Blair and thanks. I did not know about the EventSource
element but should have guesses there likely was one.
I will rethink what I am doing with the registry given your guidelines.
Especially since I just realized that my custom action, built for "Any CPU",
is running against the
Hello All:
Is it possible to author a wix file which can grant permission to a folder (not
created by the installer, as in my case, c:\windows\temp - custom asp.net app
pool a/c scenario) to a given account ?
I tried using with but it nuked the existing folder
and created a new one. -
Back in the good-old-days we simply wrote in the registry until it looked
like what this page describes:
http://msdn.microsoft.com/en-us/library/aa363661(VS.85).aspx
However, the Wix Util Extension does have an EventSource element that seems
to fit the billing. Does it not work for you?
If you i
I need a custom action to create the event source as otherwise when my 2
services and app try to write to the event log they fail. If the
services/app tries to create the event source, if it does not exist, there
is a supposed delay and the event log cannot be written to and this indeed
seems to be
Thanks!
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Saturday, October 24, 2009 5:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Can I set the Directory name attribute with a
custom property value?
That's a direct a
That's a direct assignment of the Directory name. So I expect you'll get
"[MYCOMPANYNAME]" as your directory name. Same as if you did you'd get "[MYCOMPANYNAME]". To have the
value evaluated then assigned you need to use a custom action.
In this case, a simple should
work. Or you could be more
If your default is based on Privileged you have a good solution for
defaulting perUser or perMachine.
Since the default value for the radio box is perMachine, I agree that the
next button should either set that property to perUser when the Next button
is clicked if "NOT Privileged" before it evalu
Why do you need a custom action for event logs?
Also, writing/deleting per-user content via installation packages rarely
works out as well as people hope because you can't modify all the user
profiles. Only the current user. In general, HKCU stuff should be managed by
the application.
Finally, a
There is an entire page dedicated to this topic in the WiX.chm called
"Specifying Cultures to Build". Can you provide suggestions as to what is
not clear?
On Sat, Oct 24, 2009 at 5:02 AM, Markus Karg wrote:
> Thank you for this explanation. I wish this would be told in this clarity
> in
> the Wi
The "Specifying Cultures to Build" topic in wix.chm (and on the web site)
differentiates between command-line (light.exe) and Visual Studio/MSBuild)
usages by section.
-Original Message-
From: Markus Karg [mailto:markus.k...@gmx.net]
Sent: Saturday, October 24, 2009 5:01 AM
To: 'General d
Both produ...@value and directo...@name fields are literal. If you want them
formatted you need to use custom action types 35 or 51. Those are formatted
like this:
They then have to be scheduled, according to the sequencing restrictions of
each type (if you are using then for directory paths, t
It would seem I stumbled upon exactly the same solution. Thanks for the post,
it was an interesting read!
-Original Message-
From: Richard [mailto:legal...@xmission.com]
Sent: Saturday, October 24, 2009 5:51 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using a Custom
My CA is making a web service call. So, it might be quick but it might not be
(depending on connection speed, DNS resolve times, etc.)
-Original Message-
From: Richard [mailto:legal...@xmission.com]
Sent: Saturday, October 24, 2009 5:53 AM
To: wix-users@lists.sourceforge.net
Subject:
Forgot to mention - this is with Wix 3.0 RTM (D'oh) :)
Andreas
-Original Message-
From: Andreas Mertens [mailto:andre...@nvisionideas.com]
Sent: October-24-09 7:57 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installation to limited user account failing on
WixUI_Advanced
I created an installer based on the WixUI_Advanced Dialog Set, and I am
running into the following problem.
On XP SP3, when installing to a limited user account (i.e. not admin, not
Privileged), just selecting the defaults, the installation starts and then
fails, saying you lack admin privileges.
In article
<5e7723298293ea4b8c5fac913740a9cc212aa...@tk5ex14mbxw652.wingroup.windeploy.ntdev.microsoft.com>,
Dan Giambalvo writes:
> The one thing I can't do (and didn't mention below) is actually
> changing the Windows Installer UI while still in the CA. Imagine a CA
> that takes a while
In article
<5e7723298293ea4b8c5fac913740a9cc212a7...@tk5ex14mbxw652.wingroup.windeploy.ntdev.microsoft.com>,
Dan Giambalvo writes:
> The problem I'm running into is that I can't seem to get Windows
> Installer t o re-evaluate any properties after the custom action ends.
I just covered thi
Thank you for this explanation. I wish this would be told in this clarity in
the WiX documentation.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Donnerstag, 22. Oktober 2009 02:25
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Beginner
As a suggestion for both, the WiX manual and the WiX tutorial, I want to
suggest to clearly point out this, and to make a clear distinction between
votive interpretation and command line interpretation. I read it several
times and did not find any hint that only votive is making a difference
betwee
I think the problem is that I have no knowledge with MSI before, so the
tutorial expects things that MSI experts will know, but I just do not know
(like what "advertise" means etc.).
Regards
Markus
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Donnerstag, 22
Sascha,
thank you for this tip. I will get the book. :-)
Regards
Markus
-Original Message-
From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com]
Sent: Freitag, 23. Oktober 2009 02:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Beginner's Questio
Well I flipped the order of the components in the directory node and the
feature node and still only the HKCU key got installed.
I think I will just have a custom action update/delete the registry for me
since I have to do that with event logs anyway.
- Dave
-Original Message-
From: Dave
Hi Blair, you probably meant adding KeyPath to a element.
After I did that, I got this to somewhat work but only the HKCU key gets
created and not the HKLM key. No complaints during install in the log file.
I am doing a perMachine install and it seems if anything it should do the
HKLM key and not
Thanks Rob. The curly braces did the trick.
Craig
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Friday, October 23, 2009 8:51 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Custom Action: MsiQueryProductState
28 matches
Mail list logo
