Unfortunately, I think you will have to resort to a Custom Action to get the
behavior you want. However, rather than delete files, just add temporary
records to RemoveFie table for the appropriate Component to do the removal when
you want it done. Using temporary records lets the windows
I've got most of this custom action already written, but I do the delete
directly as I never managed to figure out linking into the RemoveFile table.
Not that I put that much effort in, I was pretty wiped out after having to
figure a load of C++.
Do you have an example of this Rob? If so, I'll
Hello,
I have a radiobuttongroup (see below) and I would like to set the Property
INSTALLTYPE=0 when the RadioButtonGroup is disabled (Condition: NOT
(DEVICETYPE = 0 OR DEVICETYPE = 7)). How can I do this?
Thank's for the help!
Chris
Control Id=radioButtonGroupBox1 Type=RadioButtonGroup
I think you'd have to write a custom action. As custom
actions go, this would be a very simple one.
I tried putting in a custom action that used the cmd.exe
sleep command to fix a problem with a service that needed to
restart only to discover that not all my deployment targets
had the
Thanks for the reply, considering we already shipped 1.0.0 I guess we'll
look for a workaround...
Alex G.
On 6/25/08 6:24 PM, Blair Murri [EMAIL PROTECTED] wrote:
Properties (including public) are NOT passed to nested installations
(including RemoveExistingProducts). Your 1.0.0 installer
Hi everyone.
I'm starting to use WiX, because we're changing our deployment solution to
a MSI-based one.
So, I'm starting to recreate our previouses packages.
The first i tryed to make has to deploy files (exe) and to create shortcuts
on file that are already somewhere on network shares, in
Greetings.
I hate to barge in and immediately begin asking questions, but there's been
something eluding me that I don't quite understand. I've created a pair of
installers according to the instructions I was able to find in the docs for
successfully creating patches using pyro (extrapolating,
I will log it as a bug.
Thanks
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Thursday, June 26, 2008 3:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in dark.exe?
Sounds like a bug in
This suggestion touches the question I was thinking to ask for a long
time:
I want to perform file/registry key/etc. copy/removal at various times
during install.
I would prefer to use standard actions for that to gain automatic
rollback.
So I have to schedule standard actions to run
If I run a build through the VS IDE on the build machine, everything works like
a champ. When I run the build through Visual Studio Team Suite, Team Build, I
get the below errors...
I followed the link and information in the URL listed in the error message,
everything checks out. [But I'm
1. There is a WcaAddTempRecord(). That will do most of the work.
2. netshortcuts.cpp uses it for CreateFolder, that's pretty similar.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan O'Neill
Sent: Friday, June 27, 2008 00:39
To: 'General
I encourage you to read through the Directories topic in MSI and take a look at
the examples in WiX.chm. Using Properties that way is very non-conventional.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of THOMAS VAILLIER
Sent: Friday, June 27, 2008
Windows Installer doesn't work that way. It executes all of the rows in a
particular table in bulk.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Juricic
Sent: Friday, June 27, 2008 08:45
To: General discussion for Windows Installer XML toolset.
Try the following two blog entries:
http://blogs.msdn.com/heaths/archive/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions.aspx
http://blogs.msdn.com/astebner/archive/2007/06/07/3151752.aspx
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Oh, wait, that's the same blog entries referenced by the FAQ item you said you
read and followed below :) Never mind me... it's Friday morning.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent: Friday, June 27, 2008 10:17 AM
To:
Hey John,
Out of curiosity, do you get similar errors on a previous build? I am
curious to see if this is native to the new change or this is going to fail
in the past as well.
Thanks,
--
Brian Rogers
Intelligence removes complexity. - Me
http://www.codeplex.com/wixml/
On Fri, Jun 27, 2008 at
I received the following error reported on build 3.0.4214.0 (I think it is the
same issue, except this build of WiX didn't report all the individual ICE
action failures)
Task Light
Command:
C:\Program Files\Windows Installer XML v3\bin\Light.exe -sw1076 -loc
Hello,
I am constantly receiving this warning upon building the WIX project
file:
Warning CNDL1044: The File/@ShortName attribute's value 'PERFOR~1.XML'
is an ambiguous short name because it ends with a '~' character followed
by a number. Under some circumstances, this name could resolve to
What version of the WiX toolset are you using?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathur, Uttam
(GTS)
Sent: Friday, June 27, 2008 10:47
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Warning CNDL1044 - How to get rid of this?
I am using Wix toolkit 3.0.4220.0.
Thanks.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday, June 27, 2008 2:07 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Warning CNDL1044 - How to
We should probably add this to the FAQ. Windows Installer doesn't have such
functionality and we don't have a standard custom action in WiX to do it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nilkund Aseef
Sent: Friday, June 27, 2008 10:24
To:
The easiest fix is to remove the ShortName attribute. The WiX toolset will
generate a stable identifier that doesn't have the ambiguity problem.
PS: Is there some way to improve the error message? It's basically telling
you that you need change the short name since it could collide with
Thanks Rob but I have 5000 files (5000 rows in XML file) in my package
and I don't think this is the easiest fix. Can we assume this warning
will go away in new version of WIX?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday,
Mathur, Uttam (GTS) wrote:
Thanks Rob but I have 5000 files (5000 rows in XML file) in my package
and I don't think this is the easiest fix. Can we assume this warning
will go away in new version of WIX?
In vim:
%s/ ShortName='[^']\+'//g
No, why would we remove the warning? You're doing a dangerous thing, the
compiler is trying to help you.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathur, Uttam
(GTS)
Sent: Friday, June 27, 2008 11:19
To: General discussion for Windows Installer
Hey all, I'm trying to remove registry keys from the HKCU root for each
user.
The application is being installed for all users, however I wanted the
registry settings to be independent of each user, which is why I set it
in HKCU instead of HKLM. Now I want to remove the keys on uninstall, any
Sorry Luke, but I will be using the VIM for first time. So, how to
execute this command?
Thanks
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Luke
Bakken
Sent: Friday, June 27, 2008 2:48 PM
To: General discussion for Windows Installer XML toolset.
Yes. Dark is trying to preserve what is in your MSI as exactly as it can.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathur, Uttam
(GTS)
Sent: Friday, June 27, 2008 12:30
To: General discussion for Windows Installer XML toolset.
Subject: Re:
It is not possible to do this 100% on Windows (due to the way that roaming
profiles work).
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Micheal Wu
Sent: Friday, June 27, 2008 12:24
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] removing
Attempts to reproduce the problem failed, the problem changed to simply not
recompiling the source file in the new project.. I fixed that by specifying
different obj dirs for each project.
And I say, Wow sourceforge hasn't been updated with a new build for over a
year...
You can try using Active setup here which can do this task when user
logs into the box. But that will be pain and it's better to leave them
there.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Friday, June 27, 2008 4:33 PM
To:
IMO the danger is being overestimated.
Windows isn't that dumb. It doesn't care if all your MSI short names are
Something~1 (or any other name for that matter) because it ignores them. It's
easy to demonstrate that every time Windows sees a short name that conflicts
with one already in the
I propose that we switch to PowerShell for all automation tips.
Unfortunately, I don't have the equivalent PowerShell command handy.
It's a shame Jeffrey Snover doesn't lurk here. :D
Joel Peterson [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Joel Peterson wrote:
I propose that we switch to PowerShell for all automation tips.
Unfortunately, I don't have the equivalent PowerShell command handy.
That sounds like using a hammer for what is just a simple task with regexes and
a competent text editor - I suggested vim because I find it
Sure sure, and thanks for the tip. I was joking, though. Sorta.
Joel Peterson [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Luke
Bakken
Sent: Friday, June 27, 2008 2:28 PM
To: General discussion for Windows Installer XML toolset.
Hi,
I started to use WIX 3.0 and found link errors. Wonder if anybody may help me
what I need to do to modify my wxs file to satisfy WIX 3.0 linker.
In my wxs file I wrote as this:
Directory Id=SUBDIR41 ShortName=subDIR41 Name=vcmake
Directory Id=SUBDIR61
You know, I'd agree with you *except* that the warning was added after Office
ran into a bug that took them a long time to track down because the short name
in the MSI matched a short name of a file that already existed on the machine.
Maybe admin images? I don't remember the specifics but I
You know, I was going to do just that (create a link in the Releases to the
weekly builds) and then we had a guy say he was interested in doing the release
management. Honestly, I hadn't thought of the link in the Releases on the
weekly build until someone else suggested it a month or so ago.
MSI SDK talks about the ICE errors.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Xiaoqin Sun
Sent: Friday, June 27, 2008 15:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WIX version 3.0 errors
Hi,
I started to use WIX 3.0 and found link
In VS2008 RegExp Search Replace, use the expression (remove the outer
single quotes):
' ShortName\=\.#\ '
and replace that with a single space char... that will strip them all out.
Chris
On Fri, Jun 27, 2008 at 2:48 PM, Luke Bakken [EMAIL PROTECTED] wrote:
Mathur, Uttam (GTS) wrote:
40 matches
Mail list logo
