It might be :)
http://msdn.microsoft.com/en-us/library/aa367858%28v=VS.85%29.aspx
Action: FileAbsent Installer actually uninstalls component's files and
leaves all other resources of the component installed.
So the component as a whole is not being removed. A bit of digging turned up
this post.
Ok, I get that. As I wrote it is at worst a minor inconvenience.
However, I still need to know how I pass a command-line argument to the
application I run on ExitDialog exit.
TIA
Thomas
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 18. oktober 2011 04:53
To:
Hello,
I am building an installer where we distribute our regular software on a CD.
Then the user has an option of getting another DVD with data files on it
that I would like to go into the existing directory structure of the
software install. Would it be best to use a Patch? I do not want
Maybe it would be better to implement a 'Import data' utility in the
application instead of a setup.
Dan
-Original Message-
From: John D. Marinuzzi [mailto:nu...@hypack.com]
Sent: Wednesday, October 19, 2011 3:38 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Adding
Am 16.10.2011 23:02, schrieb John Bergman:
I believe they are located based on SDKPath. In my case, I have multiple
locations where it could be, depending on what version of the platform sdk is
installed
PropertyGroup
SDK70$(registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
I want to clarify what I was trying to say: after running the Major
Upgrade and looking at the verbose log, under the RemoveExistingProducts
action, I found a line for one of the old components that contains one
of the v.3 Assemblies - it looks like Windows Installer is planning to
remove it:
MSI
I am writing my first WiX experiments... and still learning.
When I create a directory structure for the program files I just need
the Directory/ hierarchy and the files.
When I create a directory structure for the start menu shortcuts I have
to add RemoveFolder/ items.
Why does the MSI
I'm using Burn and I got to say I love it!!!
However, it makes me want more...
I'm trying to get a legacy installation package chained and am
struggling. I would like to containerize the legacy install so my
bootstrapper is small and incremental. I've tried heat in the hopes of
it saving time
I have an MSI in a chain but Burn loaded an old local copy with the same
name. From what I understand it should not have loaded this payload
because the hash should not match. I checked the CachePayload burn code
and it looks like it doesn't check the hash if the certificate is
correct. I
Actually, the .Net v.4 GAC is not in the same location as the GAC for
previous versions of .Net.
But maybe you are right about the components. The files are in the same
directory location, but the IDs and GUIDs of the components have
changed. If that is the issue, it would be difficult to fix
Just wondering - are you getting a FileVersion value in any of the
MsiAssemblyName tables in any of these MSI files? I can't quite get my head
around it, but in-place updates of a GACed assembly will happen when
FileVersion is there, and if the GAC's location has moved then some parts of
Yes, in the MsiAssemblyName table there are fileVersion and version
records for each assembly. I remember running into problems with
side-by-side installation of assemblies in the past, and we fixed that
by versioning our .Net dlls. Up until this change to .Net v.4, our
Major Upgrade has been
12 matches
Mail list logo
