I've encountered this. I had to shorten names that that the full path is less
than about 240 in order to get past the problems I was having.
That means that your current path of your wix file, and append your relative
pathing and see how long the resulting string is, maybe you are beyond the
l
Hi,
I am hoping someone can help me here. I am defining a component with a file
like this:
I am using the visual studio 10 to do this. When I build the
project, I get an error on this component only (I have loads of others that
work fine): The system cannot fi
Thanks Palbinder.
What are the consequences of targeting earlier vs. later versions of
Windows Installer, other than if you specify a greater number than the
Windows Installer version, earlier versions won't load it?
The software itself supports Windows 2000-Windows 7, which is why we
target 2
That will work.
--
John Merryweather Cooper
Jack Henry & Associates, Inc.
Build & Install Engineer - jXchange
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
Sent: Wednesday, November 09, 2011 2:0
How do you set the Component guid to null? Do you mean an empty string?
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Wednesday, November 09, 2011 12:34 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Keeping files aft
Beware though because many people get the impression that permanent is a
project setting, and consequently they install the same file later with
permanent = fale and expect it to uninstall. Permanent means permanent on the
system, forever ref counted by MSI to stay there.
IMO a better solution
On 08/11/2011 19:03, Bruce Cran wrote:
> light.exe : error LGHT0001: Illegal characters in path.
> [C:\cygwin\home\mymsi.wixproj]
It turned out that I had a stray " in one of my variables which was
being used in a path.
--
Bruce Cran
I'm currently finding myself in a bind, where I wish to generate a
shortcut with a property value embedded within it. From the various
posts and observation, I note that the Shortcut table isn't
"formatable". As such, I can't use property references within the name,
description, etc fields. My fi
Hi,
With my setup program I install some files to a network share. I also have a
custom action that edits a file after it gets installed with the install
location(deferred custom action called by a C++ dll).
When the deferred sequence kicks in, the MSI performs actions as the system
account. But
First you need to target Windows Installer 4.0 (or later which means 4.5 on
pre-Vista platforms) if you want to make a single package which can do per-user
& per-machine installations. This will involve bootstrapping the 4.5
redistributable for pre-Vista SP2 platforms.
The code you pasted shows
use permanent="yes"
Example:
also DON'T use because this is
cleaning your folder.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Keeping-files-after-uninstall-tp6975689p6977419.html
Sent from the wix-users mailing list archive at Nabble.com
Hi, I have a burn bootstrapper bundle that includes a Fragment that I took
from the Wix sources to deal with installing .Net framework 4. Now this,
together with VC++2010 and other things are dependencies I need, but I
don't want them to be uninstalled when my app bundle in uninstalled.
So I've go
12 matches
Mail list logo
