It looks like you file attribute is wrong, it is set to WebConfigFilePath but
this seems to be set to #f_6da07eb4 - is that a File/@Id, if so then that
should be in the XmlConfig/@File attribute.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Hi,
I'm trying to modify the Browse_Dialog to check whether the selected
directory allready exists on the users computer and display a warning if
it exists. I'm not an WiX expert and so I would be happy if anyone could
give me some hints how that could be done.
Thanks
Andreas Hellwig
Hi,
I am writing some custom action by using DTF. I have id of file from
File table.
The question is:
How I can know what is the final location of this file after intall.
Thanks for advance,
Dima
-
This SF.Net email
Windows Installer supports multiple instance installation, but the question I
have is do you need multiple instances of your product or only multiple
instances of your database?
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread
Hi All,
While installing a product, I want to add few extra registry entries
if the OS is Windows Vista. To achieve this, I created my .ddr file as
given below..but its not working. Am i missing something? Any help
will be highly appreciated..
?xml version=1.0 encoding=utf-8?
Wix xmlns..
anyone? :)
--
View this message in context:
http://www.nabble.com/Rollback-CustomAction-Question-tp18448323p18589420.html
Sent from the wix-users mailing list archive at Nabble.com.
-
This SF.Net email is sponsored by the
Your rollback script will only be invoked if failure was realized after your
rollback script was scheduled.
Bear in mind, the Immediate vs. Deferred execution context. Rollback happens
only in the deferred sequence.
So, is your failure that you fake in the deferred sequence after
This won't work because you're using a pre-processor check for your condition,
which happens at the time you build the MSI, not at the time you run it.
You need to do the check by adding a Condition element to the Compnent
element that I assume eventually includes the Registry snippet below.
Sorry, didn't have time to do anything with DTF yet, but from the MSI point of
view you need to use formatted
(http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx) value.
Depending on what exactly you need - file path or folder path, you use either
[#filekey] or [$componentkey].
The default UILevel for uninstall appears to be 3 (Basic). I need to run at
UILevel 5 (Full) in all cases but 2 (None).
I have tried adding a custom action to the InstallExecuteSequence that changes
the UILevel property to 5 - checking the setup log, I can see my custom action
runs and the
As Bob, of Joy of Setup fame, explained here once, there is no way to
change the level used by ARP and UILevel is read-only during uninstall.
However, you can add Change ARP option which would launch your authored
Change dialog from which you can proceed to a full UI uninstall (or
repair or the
I also have the advantage (disadvantage?) of scale to inform my opinions.
smile/ I routinely have to deal with projects the size of Office, SQL Server
and Visual Studio so there is plenty of opportunity for cosmic rays (Murphy's
law?) to sneak in and blow the quick but incomplete (hack?)
I am using NAnt to build my WiX project. Here is the code:
target name=CreateSetupPackageUsingWiX description=Create the
installer package using WiX Script
mkdir dir=${wix.release.dir}/
loadtasks
assembly=${wix.work.dir}/Microsoft.Tools.WindowsInstallerXml.NAntTasks.
dll/
candle
I assumed you are talking about uninstalling via ARP. Otherwise the
batch file with the following content works just fine in my daily
testing:
msiexec /x myproduct.msi /qf /lv*x .\install.log
qf is for full UI and you can put product code instead of msi filename
since you are not supposed to
Or am I, for the time being, still better off with the old-style
administrative installs and PatchCreation?
In my case binary delta is the requirement.
Thanks
-Original Message-
From: Tony Juricic
Sent: Monday, July 21, 2008 2:08 PM
To: wix-users@lists.sourceforge.net
Subject:
I'm using the release version of WiX v2 (2.0.5805.0) and need to install
a certificate to the local machine's Trusted Root Certification
Authorities certificate store and the Trusted Publishers certificate
store - the equivalent of
certmgr.exe -add cert.cer -s -r localMachine root
certmgr.exe
One option to consider is using the shipping MSBuild .targets file that has a
complete build process for WiX in conjunction with NAnt. Trying to re-construct
a build process using individual tasks is often fraught with peril, and using
the one that ships with WiX is almost always a better idea.
Yeah, my primary concern is ARP. So I've set ARPNOREMOVE and ARPNOREPAIR so
that modify is the only option. That's invoking my normal UI, so that's more
or less all I need. Thanks for the tip.
-J
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony
TrustedPublishers was added to WiX *v3* jus this last week. No plan to add the
feature to WiX v2 (since it is stable and we're not adding features there).
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Farrell
Sent: Tuesday, July 22, 2008 14:57
Thanks Rob, looks like Ugly CA Time again then ...
Regards,
jjf
From: Rob Mensching
TrustedPublishers was added to WiX *v3* jus this last week.
No plan to add the feature to WiX v2 (since it is stable and
we're not adding features there).
-Original Message-
In the past I've found CAB files in the MSI's Binary table, and used
Orca to extract the CAB, then used Windows Explorer to get at the
contents. But the MSIs produced by the WiX toolset on a project I've
inherited don't have a CAB visible anywhere. The binaries are definitely
inside the MSI,
21 matches
Mail list logo
