See How to create an uninstall shortcut (and pass all the ICE
validation).
http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninstall-
shortcut-and-pass-all-the
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: 25 October 2010 21:09
To:
Not with WiX.
I've seen other installation creation suites doing something like that
but you'll need to buy licenses to use them.
Windows Installer needs every file declared within the MSI for it to be
able to install them, any package which doesn't require you to do this
yourself is simply
The service executable installed will point to the KeyPath for the
Component. Therefore, you must ensure that the correct executable is
either the first child File element under this Component or explicitly
mark the appropriate File element as KeyPath='yes'.
From the Remarks section at
Hi,to all
i am facing some problem while deleting folder created by installer,
i want to delete folder with custom action i tried to do it with calling
cmd RD /s /q /path but its not working so i tried with VBscript,
it worked for some extent as i was providing path which was hardcoded,
i want go
Hi Palbinder
I thought this would be the case.
Thanks for your time
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 26 October 2010 10:39
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] run time harvesting
Not with WiX.
Hi,
The properties defined in your MSI (explicitly or at runtime) are
available from a VBScript using the Session variable. What you need
to do is set a property with your path. Your install location is
typically INSTALLDIR. If you're using the WixUI_InstallDir UI then
the work of setting
Thanks that's what I figured. It would be nice to get an error if you
make the mistake of not locating your ServiceInstall in a component with
an executable.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, October 26, 2010 3:57 AM
To: General
I managed to understand the usage of HEAT and i saw the output of that tool
is to a wxs file which changes the structure with in. Since i am just
starting to use wix, pardon my understanding. As i understand, i have a wxs
file and the heat tool also outputs to wxs file. my question is Should i be
Hello everyone,
I had typically been building with devenv.exe within the Visual Studio IDE. The
couple *.vdproj projects I'm working with produced both an MSI and a setup.exe
after building. I am attempting to use WIX to build the MSI for automated daily
builds right now and have decompiled
I think it would be really useful to have a ComponentRef of some kind so we can
split up file harvesting from actions that apply to some components.
ServiceInstall is just one example of this. Another common one I run into is
XmlFile and XmlConfig. The Xml elements can be placed in a component
Hello WiX Users,
I am trying to find documentation regarding how I can use WiX to register a
custom developed managed module for an IIS 7 web site. I am using WiX 3.5 for
this installation.
I have successfully registered the module by hand but I would like to use WiX
to automate the process.
Something along the lines of this:
http://wix.sourceforge.net/manual-wix3/install_dotnet.htm ?
Also, the Windows SDK has a tool (WiDiffDb.vbs) that does a diff between two
MSIs. Either smoke.exe (from the WiX toolset) or MsiVal2 or even the Orca
tool (from the SDK) can run validations.
Hi Blair,
I've ran WiDiffDb.vbs and found one inconsistency which I will work to resolve.
The link you gave regarding the bootstrapper is very helpful as well.
Thank you for your time and response!
Regards,
Chris
From: os...@live.com
To: wix-users@lists.sourceforge.net
Date: Tue,
Hi,
I used to use 3.5.1623. I have upgraded to 2215 and did a clean up on our
tree (we had several versions of v3 wix assemblies checked in).
I have the following scenario: I have Compile Include=Components\*.wxs /
at my wixproj. Initially this folder is empty. I have a BeforeBuild target,
14 matches
Mail list logo
