If you can wait a few more weeks, this might be an interesting thing to
incorporate into WiX v4. If interested, ping me and I can connect you with
the correct people at Outercurve (who maintain the WiX assignment process
now) to get the process rolling.
On Mon, Nov 12, 2012 at 9:05 AM,
The .idt didn't seem to stay attached. Can you upload it somewhere else to
be shared?
On Fri, Nov 9, 2012 at 1:17 AM, Sami Ovaska sami.ova...@mirasys.fi wrote:
Hi,
I’m getting error
C:\Users\SamiOvaska\AppData\Local\Temp\jmbjxkqj\_Validation.idt : error
LGHT0136 : There was an error
Hi Rob,
.idt can be found in https://dl.dropbox.com/u/24850494/_Validation.idt
Regards,Sami
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 13. marraskuuta 2012 10:06
To: General discussion for Windows Installer XML toolset.
Subject: Re:
I posted of this a while back. You've been a lot more persistent than
me in cutting and pasting the code. I gave up and downloaded this
tutorial book instead:
http://www.packtpub.com/article/getting-started-with-windows-installer-xml-wix
It was worth it for me, but you're near the end, so maybe
This is certainly possible.
1. The WixUI_InstallDir built-in dialog set will prompt the user for an
installation location.
http://wix.sourceforge.net/manual-wix3/WixUI_installdir.htm
You may even be able to detect the location of the existing tool, if you know
the MSI product codes of the
I am getting the following error from the C#/DTF custom action when running on
Windows 8 without .NET 3.5 installed:
SFXCA: Failed to get requested CLR info. Error code 0x80131700
SFXCA: Ensure that the proper version of the .NET Framework is installed, or
that there is a matching
To answer my own question...
It was a couple of things:
1. The config was called app.config so needed to rename it to
CustomAction.config
2. The Build Action property needed to be set to Content.
Neil
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 13
Did anybody write their own BA for wrapping an msi? I want to show the msi
UI not the Burn UI and apparently this is the only answer.
Thanks, Dan
--
Monitor your physical, virtual and cloud infrastructure from a single
Ok. Is it also true that the burn package on x64 machine takes longer (to
complete install) than on x86 machine when its run. Is this a known issue or
can I probe to try and improve my the package performance for x64 platform?
Thanks much for your insight.
Syam
-Original Message-
What about using a Feature/Condition instead?
On Tue, Nov 13, 2012 at 1:40 AM, Bruce Cran br...@cran.org.uk wrote:
Is there currently any simple way to associate a checkbox with feature
installation for a specific MSI? From what I've read the only way would be
to do conditional installation
Do you think the build could have figured that out and helped you with
error messages?
On Tue, Nov 13, 2012 at 4:52 AM, Neil Sleightholm n...@x2systems.comwrote:
To answer my own question...
It was a couple of things:
1. The config was called app.config so needed to rename it to
I've never noticed that myself before. A Burn log file should show you what
is taking the time. I do not know why Burn's code would behave
differently... but if you find something consistent maybe it is a bug in
Burn on 64-bit (or something in your Chain).
On Tue, Nov 13, 2012 at 7:16 AM, Syam
Probably not, this was a project with its origins in the first release of DTF.
I added app.config because that is what I would do with an application, it was
only when I created a new custom action project from the template that I
thought that the name might have been relevant and then I
Hi,
This is what I do:
!-- Check for .NET 4.0 --
PropertyRef Id=NETFRAMEWORK40FULL/
Condition Message=Requires the Microsoft .NET Framework 4.0. To download
the requirement please visit:
http://www.microsoft.com/en-us/download/default.aspx then restart the
$(var.ProductName)
How do I skip the Welcome Dlg when customizing Mondo UI?
Can I skip the Exit Dlg?
Thanks,Dan
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers,
My msi uninstalls a component when repair is clicked. I have a custom
action for uninstalling this component and in the InstallExecuteSequence I
have the condition:
Custom Action=Uninstall_Component After=RemoveRegistryValues
![CDATA[Installed AND NOT REPAIR]]
/Custom
There is some info here that might help you:
http://neilsleightholm.blogspot.co.uk/2008/08/customised-uis-for-wix.html
Neil
-Original Message-
From: Liviu Dan [mailto:nliviu...@gmail.com]
Sent: 13 November 2012 19:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Skip welcome
Neil,
Thanks for your reply. I already looked at the link you provided; it is a
good example of how to skip a dialog by not publishing it and changing the
back and next controls to point somewhere else; but the welcome dlg is the
first one and it is called by some install sequence event not by a
Why don't you just replace the first one with the one you want but give it
the welcome name?
Neil
Neil,
Thanks for your reply. I already looked at the link you provided; it is a
good example of how to skip a dialog by not publishing it and changing the
back and next controls to point somewhere
19 matches
Mail list logo
