Hi,
I believe windows installer will not accept major version greater than 255.
If we specify, we will encounter error like below:
error CNDL0242: Invalid product version '2014.1.2.3'. Product version must
have a major version less than 256, a minor version less than 256, and a
build version less
Component/@Guid must be globally stable (the global part of global unique
identifier should kinda' hint at that). Component/@Id must be stable for
patching/minor upgrades.
___
FireGiant | Dedicated support for the WiX toolset |
Oh, you have to generate a new component ID? Is that the trick? I had forgotten
that. Hm, that's going to be interesting for our front end thing to keep track
of, since it makes componentids as it goes for everything so that the WXS can
be automatically generated from a list of files and
You should read:
http://robmensching.com/blog/posts/2003/10/18/component-rules-101/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: keith.doug...@statcan.gc.ca
If the app is modifying the files, the RemoveFIle should be in the MSI for the
version that installed the file. The real question is why is your app modifying
the installed files. Could it not be changed to use the default file if an
override didn't exist? Then have the app copy the installed
No, I created the wxs file manually.
Regards,
Tarun
-Original Message-
From: keith.doug...@statcan.gc.ca [mailto:keith.doug...@statcan.gc.ca]
Sent: Friday, June 12, 2015 4:32 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to remove empty xmlns attribute
Are you
We have some applications which will be changing the actual files they install
as they upgrade in the sense that new names will be used.
I notice that my default way of doing the upgrades does not *delete* the old
ones. (I.e., creating a new WXS with the same upgrade code as the old one but
Yes it's correct that the ProductVersion docs say the maximum major
version is 255. Even if you make it larger in Orca you'll still get an
ICE error if you run validation ICE24 ERROR ProductVersion:
'2014.1.1' is an invalid version string.
(Thanks to Rob's post, too.)
But: I am not sure why I read both the post, the WiX documentation (under
Component), but it sounds like to me that the Guid attribute on Component is
what is supposed to be stable, not the ComponentId.
Nevertheless, I have written a new mechanism for generating
* works well, and follows the component rules.
-Original Message-
From: keith.doug...@statcan.gc.ca [mailto:keith.doug...@statcan.gc.ca]
Sent: Friday, June 12, 2015 12:32 PM
To: keith.doug...@statcan.gc.ca; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Removing files as part
Anecdotally, we have a release based on 3.8 and I tried a patch using 3.9
(the release just prior to 3.9r2) and ran into some odd problems which were
resolved by sticking with 3.8. I think I posted something about it to the
list a while back.
Rob Mensching-7 wrote
It will probably work but you
Dear Team,
I am trying to add new element in one existing xml file using Wix installer. My
xml file content is as follows:
?xml version=1.0 encoding=utf-8?
PROCESSLIST xmlns:i=http://www.w3.org/2001/XMLSchema-instance;
xmlns=http://schemas.datacontract.org/2004/07/BusinessWorkflow.Contracts/
Are you generating your wxs file by programmatically creating a .NET XML
object? I discovered that when I did that I got the xmlns attribute everywhere
*unless* I set it deliberately on each tag programmatically. Then and only then
it doesn't appear on anything but the WiX tag. I am sure
Hello Experts,
I have a simple question about upgrades and a condition I am using.
I have two MSIs A and B. (A is old and B is new)
When I upgrade A with B, A was written a long time ago by someone else and
they mismanaged upgrades, so I am trying to recuperate application generated
files.
14 matches
Mail list logo
