Top of the Morning to you,
I'm trying to generate a complete Installer using the command-line
tools. I have the directory structure. I am porting the Installer from NSIS.
I need 6 components, and would like to use the MondoUI.
Could you please give me some ideas on how to get started, and
One option: After the dialog, schedule a SetProperty custom action that sets
NEED_CONFIGURE_FIREWALL to 2 (or 0, if you prefer) if it is missing or
blank. Before showing the dialog (but after AppSearch) schedule a
SetProperty custom action that clears the value if it is set to your
sentinel value.
There are ideas and some sample code in the docs, there's a good tutorial
that introduces most of the basic features (with lots of sample code and all
using the command-line tools), and there are several blogs (some listed on
WiX's SF site and all accessible using internet searches) with sample
Hello,
this is more an MSI than WiX related issue but I have seen many general MSI
question with good answers, so I try this also.
I have an msi installation that exits with error 1625, but only on a small
number of machines. The same installation file works well on all others.
Here is the
Sorry, probably an email filter! Attached again.
It was a 32-bit MSbuild.
I didn't know there were two.
I tried the 64-bit and got the same result - both logs attached.
Thanks for helping.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 13 August 2010 17:56
To: 'General
http://lmgtfy.com/?q=WiX+Tutorial
Palbinder Sandher
Software Deployment IT Administrator
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.
I think your actual error may be happening earlier in the log than the pasted
section. According to MSDN there is no error 1625 -
http://msdn.microsoft.com/en-us/library/aa372835.aspx
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
Look at the Note regarding 2720. That is telling you that an API attempting
to set a source directory failed. The OS returned error 2 to that API
internally. 2 = The system cannot find the file specified..
Are you running this MSI from a share? Are drives mapped differently for
different users
It appears to me (based on the error message) that MSBuild does not think
that items can/should have metadata named Value.
Typically, when adding entries to an item, the value of the Include
attribute varies, since that attribute's value is the identity of each entry
in the item list.
I suspect
Hi Blair,
I'd had those sections working before on another computer (32-bit), so I
don't know why I was getting the errors.
Thankfully I took your advice and the error went away (or at least
somewhere else lol).
Thanks for your help!
Regards,
Matt
-Original Message-
From: Blair
If it really is the 1625 returned for the policy error, it looks like the
DisableMSI policy at the system or user level. Other policies can matter too,
maybe DisableBrowse if it's associated with the source location as the log
seems to indicate.
I am receiving the following error:
C:\Program
Files\MSBuild\Microsoft\WiX\v3.5\Wix2010.targets(1770,5): error MSB4018:
The RefreshGeneratedFile task failed unexpectedly.
Running Wix 3.5.1930 just downloaded and installed last week.
I see a thread back in February where
All,
I'm still relatively new using WiX but it seems to have everything I need...
but
I'm struggling with getting a .MSI file to upgrade the way I want.
I have two versions of my product - one Free version which has limitations
and
one Registered full version.
I know which version I'm
Here is some more information on what I've tried.
I've tried to set the UpgradeCode in Product based on which version I'm
building and then provide two Upgrade blocks with the different ids...
?
?
?
?
?
if$(var.Edition) = FreeVersion?defineMyUpgradeGUID =
I want to execute a custom action when the installation fails and a
rollback is executed by the MSI, but my custom action doesn't run
although I set it to execute on a rollback.
Here is my code:
InstallExecuteSequence
Custom Action =DeleteDbBackupFileOnRollback After
=InstallFiles/Custom
Rollback custom actions are written to the script and if there is a failure in
script execution the Windows Installer will walk the script backwards and
execute any rollback CA's that have been written to the script. So make sure
you schedule it early enough ( possibly well before InstallFiles
16 matches
Mail list logo