Minor update:
saute [before] [after] [result.wxs] options
Options:
--noUninstall : do not generate uninstall create delete commands.
Pre-process:
Parse both before and after into xml documents. i.e. validate
they're well-formed.
Validate any schemas.
Process (starting at root)
1. Look for
Maybe you should step back and describe the fundamental problem that
you're trying to solve. Perhaps then someone might be able to suggest
an alternative 'solution' that doesn't require msi name.
Regards,
Tim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Hi,
I have a configuration file in which I need to fill in some values at
install time. Eg:
plugins:logging:output = ${LOGS_DIR}/log.txt;
Is token replacement possible in WiX / msi? Is is possible to replace
${LOGS_DIR} with a value natively in wix / msi?
Thanks,
Stephen Mooney
Hi,
is there a way to prevent all SQL scripts called on product uninstall when
doing a major upgrade to new version ? I can not change the older version
MSI. I would like to solve it in the new version. I have tried to comment
out Upgrade element but it results in two products with the same
Great nights with your woman are now possible.-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
In article [EMAIL PROTECTED],
RAYMENT Tim [EMAIL PROTECTED] writes:
Maybe you should step back and describe the fundamental problem that
you're trying to solve. Perhaps then someone might be able to suggest
an alternative 'solution' that doesn't require msi name.
...or a custom action.
Which, according to the documentation can only be: Local, Source, or
Either. No Unavailable.
Ok. At least I know now.
Thanks Bob.
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 23, 2008 12:32 PM
To: Robert Priest
Cc: wix-users@lists.sourceforge.net
Subject: Re:
Hi all,
I've two questions. I tried to solve them by myself, but I cannot find
informations in the net...
1) How can I prevent a registry key from being removed during uninstall?
2) What do I have to do, that a only not existing registry entries (some
REG_SZ's) will be create during install.
Well it took me about six hours of websearching and following false
leads to get the pretty easy custom action working, so just to try
and save anyone else the effort in the future...
I figured out almost immediately that you _can_ perform the action
fairly simply using the following:
Property
1)
I'm assuming by 'registry key' you mean any value/data pair. The 'key' is
strictly a container for values (one of which can be the default value). If
the key is empty - contains no values and the default value has no data -
then Windows Installer deletes the key.
To keep values even after all
I was fairly sure that if you set ARPSIZE it sets the EstimatedSize property
that Raymond talks about at
http://blogs.msdn.com/oldnewthing/archive/2004/07/09/178342.aspx, and
therefore ARP doesn't need to guess at the right thing to look at to check
the size.
Since Windows Installer knows
I'm currently trying to adapt our performance counter text string
registration from being done in our own code (picked up from Jeff Richter's
book Programming Server-Side Applications for Windows) to use the
LoadPerfCounterTextStrings API and, ultimately, the PerfCounter element in
WiX. Something
Not currently, no. If you choose to develop one, be sure to reset the
modification timestamp back to the creation timestamp (or set the
creation timestamp to the modification timestamp) or you will not be
able to replace that file by default again since MSI default file
versioning rules won't
Hey Stephen,
There is a crude version of something like this I wrote. I call it Property
Loader, I am sure you could modify it a bit and get what you want.
http://www.codeplex.com/WIXML/Release/ProjectReleases.aspx?ReleaseId=263
Thanks,
--
Brian Rogers
Intelligence removes complexity. - BR
14 matches
Mail list logo
