ndows Installer XML toolset.
Subject: Re: [WiX-users] Dealing with ICE48 warning
Open the MSI up in Orca or Inst Ed and you might find that the directory IDs
in the merge modules have had Guids added to them. Ids in modules are
"modularised" to avoid name clashes.
-Original Messag
1 23:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Dealing with ICE48 warning
Hi Peter...
It was a bit of a nuisance to get a verbose log out of the wmi
install, so I've been comparing the logs from the builds using the type 51
and type 35 work-around
27;s a good reason for it. A comparison of verbose logs may give you a
clue.
-Original Message-
From: Mark Modrall [mailto:mmodr...@mzinga.com]
Sent: 04 October 2011 16:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Dealing with ICE48 warning
Thanks, Pe
of verbose logs may give you a
clue.
-Original Message-
From: Mark Modrall [mailto:mmodr...@mzinga.com]
Sent: 04 October 2011 16:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Dealing with ICE48 warning
Thanks, Peter... I can give it a shot.
I was a bit perp
45 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Dealing with ICE48 warning
I've just looked back at your original post which is how to avoid ICE48
errors. The ICE48 error is issued because ...
ICE48 checks for directories that are hard-coded to local pa
o: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Dealing with ICE48 warning
I was wondering maybe *before* CostFinalize? I'm just grasping around
here...
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, October
Mark
-Original Message-
From: jhennessey [mailto:jack.hennes...@hyland.com]
Sent: Monday, October 03, 2011 4:48 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Dealing with ICE48 warning
When you use a type 51 custom action it doesn't call MsiSetTargetPath because
you&#x
: Re: [WiX-users] Dealing with ICE48 warning
Could it be the file's encoding ? Declared as UTF-8 but written in something
else maybe ?
-Original Message-
From: Mark Modrall [mailto:mmodr...@mzinga.com]
Sent: 04 October 2011 15:17
To: General discussion for Windows Installer XML to
riginal Message-
From: jhennessey [mailto:jack.hennes...@hyland.com]
Sent: Monday, October 03, 2011 4:48 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Dealing with ICE48 warning
When you use a type 51 custom action it doesn't call MsiSetTargetPath because
you've told it y
---
From: jhennessey [mailto:jack.hennes...@hyland.com]
Sent: Monday, October 03, 2011 4:48 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Dealing with ICE48 warning
When you use a type 51 custom action it doesn't call MsiSetTargetPath because
you've told it you are setting
When you use a type 51 custom action it doesn't call MsiSetTargetPath because
you've told it you are setting a property and not a directory. Try using a
type 35 custom action (after CostFinalize) by using the Directory attribute
instead of Property.
--
View this message in context:
http://windows
he right
places?
Thanks
Mark
-Original Message-
From: Mark Modrall [mailto:mmodrall@...]
Sent: Wednesday, September 28, 2011 3:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Dealing with ICE48 warning
Hi...
Our installers are used internal
hanks
Mark
-Original Message-
From: Mark Modrall [mailto:mmodr...@mzinga.com]
Sent: Wednesday, September 28, 2011 3:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Dealing with ICE48 warning
Hi...
Our installers are used internally to install
Hi...
Our installers are used internally to install to a farm, so we
had
In our old Wix 2.0 scripts. We recently updated to Wix 3.5, and I started
getting ICE48 warnings. I googled around on how to do this "properly", and I
found some posts about moving the definition of th
14 matches
Mail list logo
