Bugs item #1380628, was opened at 2005-12-14 19:15
Message generated for change (Comment added) made by ubeierlein
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1380628&group_id=105970
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: dark
Group: v3.0
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Uwe Beierlein (ubeierlein)
Assigned to: Rob Mensching (robmen)
Summary: Custom Action Types 23 & 39: Atributes not recognized
Initial Comment:
Hello,
background:
it is required to create a MSM from MSI file via dark.
The MSI package contains nested installation CA's.
Dark did a good job and created the wxs xml file.
The problem:
candle can not interpret some attributes:
syngo.wxs(43690) : error CNDL0004 : The CustomAction
element contains an unexpected
attribute 'PackageProductCode'.
syngo.wxs(43690) : error CNDL0004 : The CustomAction
element contains an unexpected
attribute 'InstallProperties'.
syngo.wxs(43691) : error CNDL0004 : The CustomAction
element contains an unexpected
attribute 'PackagePath'.
The corresponding lines of the wxs:
<CustomAction
Id="Med_Nested_Remove_sw_msxml_5_3962197254_Code"
Return="check" PackageProductCode="{716E0306-8318-4364-
8B8F-0CC4E9376BAC}" InstallProperties="REMOVE=ALL" />
<CustomAction
Id="Med_Nested_AddLocal_sw_msxml_5_305851640_Source"
Return="check" PackagePath="3rd_party.msi"
InstallProperties="ADDLOCAL=ALL" />
<CustomAction
Id="Med_Nested_AddLocal_sw_msxml_5_305851640_Media"
Return="check" PackagePath="HookDir\3rd_party.msi"
InstallProperties="ADDLOCAL=ALL" />
It seems that this topic has not yet been implemented
in candle. I did not attach the wxs, because it is to
huge.
Best regards, UBeierlein
----------------------------------------------------------------------
>Comment By: Uwe Beierlein (ubeierlein)
Date: 2006-02-24 09:53
Message:
Logged In: YES
user_id=1405012
Bob, I agree that nested installs are mostly bad, but in
some rare cases, they are useful. Even Microsoft does not
discontinue nested installs, but just recommends not to use
them.
That is the point. There is a difference between 'not
recommend' and 'disable'. I would make it a decision of the
package autor and not a decision of the toolkit developers.
----------------------------------------------------------------------
Comment By: Bob Arnson (barnson)
Date: 2006-02-24 05:01
Message:
Logged In: YES
user_id=26581
The point of the guidelines is that nested installs are bad.
Whether there's an MSI replacement, they're still bad.
Nested installations can be replaced -- without the risks --
using a chainer/bootstrapper.
----------------------------------------------------------------------
Comment By: Uwe Beierlein (ubeierlein)
Date: 2006-02-23 10:00
Message:
Logged In: YES
user_id=1405012
Thank you for the very interesting link, barnson.
I know that nested installs are problematic. Windows Vista
has Windows Installer 4.0 included, introducing the MSI
chaining feature.
As far as I know, Windows Installer 4.1 will be the next
available redistributable package for current platforms
(e.g. Windows XP).
So it is a long time until that MSI-chaining feature get
available for current platforms. Thus I suggest to support
nested installs again, but to raise a (nagging) warning in
the logfiles.
Programmatically, it's not a big deal to enable nested
install's again. Not implementing nested install's does not
really prevent package author's from inserting them via
transformations. The only thing is the additional packaging
step and the process documentation overhead.
----------------------------------------------------------------------
Comment By: Bob Arnson (barnson)
Date: 2006-02-22 21:27
Message:
Logged In: YES
user_id=26581
See
http://blogs.msdn.com/jmazner/archive/2006/02/17/534373.aspx
for a link to "Proposed Requirements for the Windows Vista
Logo Program for Software," which says:
Nested install custom actions (type 7, type 23, and type 39)
have proven to be excessively problematic for application
installs. Do not use these types of custom actions.
----------------------------------------------------------------------
Comment By: Uwe Beierlein (ubeierlein)
Date: 2006-02-01 09:02
Message:
Logged In: YES
user_id=1405012
Hello,
I know that nested installations can be evil, but in
some cases they make sense.
Please remember: merge modules have nearly the same issues
and you still support them. Merge Modules are responsible
for the success of the "Slammer" Virus, because the hotfix-
spreading was blocked due to this technology.
So I suggest to consistently implement the support
for "nested installations" in all modules, again.
Candle can raise a warning during compilation like
"Nested installations may require some preparations in
the referenced package and may confuse the user because
update, upgrade and uninstallation are handled
by the hosting package."
> Nested packages have been deprecated by the
> Windows Installer.
Not deprecated by the Windows Installer, but only
by some members of the WiX community.
As long as MSI chaining has not been implemented in
Windows Installer, "nested installations" may be used
to workaround this issue.
So please make "nested installations" a decision of the
user and not a decision of the community. Otherwise you
will have to remove support for merge modules and (all)
Custom Actions, as well.
Best regards, UBeierlein
----------------------------------------------------------------------
Comment By: Rob Mensching (robmen)
Date: 2006-02-01 05:35
Message:
Logged In: YES
user_id=991639
Nested packages have been deprecated by the Windows
Installer.
----------------------------------------------------------------------
Comment By: Bob Arnson (barnson)
Date: 2005-12-16 07:15
Message:
Logged In: YES
user_id=26581
Candle no longer supports nested installations -- they're
deprecated. The bug is that Dark should not generate the old
WiX source code for nested installs.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1380628&group_id=105970
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
