I got my 64 bit C# Custom Action running just fine and it can set some
properties that I can use to set my account and password on my
ServiceInstall element. Thanks to everyone. Wix is pretty cool!
I have two other questions though:
1. When my CA sets properties they print in the log How can
1. There are several issues that are resolved by using DTF to run managed
code custom actions, among which is a problem whereby if a custom action
instance of msiexec loads the managed runtime and is reused for a different
action, it can't load a different version of the runtime (if needed). By
To report what I found on my questions:
1. I guess the !(var.Property_XXX_Password) syntax is a pre-processor
variable and not a property!
2. Property Id=Property_XXX_Password Hidden=yes/ --- this worked to
hide the password was replaced with *'s!
- Dave
-Original Message-
From:
Good information thanks!
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Sunday, October 11, 2009 3:01 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Which way to install a Windows service is best?
1. There are several issues that
I see at least 4 ways my windows service could be installed.
My goal is to be able to call some custom code so that I can set the
username and password for the service by looking up and decrypting a value
from the registry. Therefore I do not think that ServiceInstall is an
option. The
Why no use ServiceInstall etc to install the service, but then change the
appropriate user info via the WiX registry calls?
That way MSI is in charge of correctly uninstalling and removing the
appropriate registry settings.
Dominique.
-Original Message-
From: Dave Kolb
I would love to but the information I need to look up is actually the
service account and password that goes onto the ServiceInstall element.
Once the service is installed I think it is too late to change this
information. At least I don't know where Windows keeps it, or the format it
is stored in
Guten Tag Dave Kolb,
am Samstag, 10. Oktober 2009 um 19:24 schrieben Sie:
I would love to but the information I need to look up is actually the
service account and password that goes onto the ServiceInstall element.
Once the service is installed I think it is too late to change this
Guten Tag Thorsten and thanks.
I have not built a custom action yet but will look at that approach iff my
custom action can set WIX properties that another custom action or wix
element can use afterwards.
If I can run my CA before the ServiceInstall element then it could just
refer to the
If I were you I would use option 4. I would write an immediate CA that
retrieves and decrypts the account and password that I would schedule in
InstallExecuteSequence running sometime before the InstallServices action (I
would probably sequence it before CostInitialize, but that is just me).
That
Thanks Blair. I will have a go at using ServiceInstall and running a prior
CA to set properties for it and will avoid any evil self install patterns. I
am confused on how DTF fits into the picture though.
1. Is DTF necessary to run a custom action built with C# managed code?
2. Must I supply my
I did find this
http://blog.torresdal.net/2008/10/24/WiXAndDTFUsingACustomActionToListAvaila
bleWebSitesOnIIS.aspx so think that will suffice for an example to get
started. Any others appreciated though. Apparently DTF supplies the
conventional .dll wrapper msi needs to call managed code. Needs to
12 matches
Mail list logo
