Feature Requests item #956969, was opened at 2004-05-19 12:13
Message generated for change (Settings changed) made by derekc
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=956969&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: None
Group: None
Status: Open
>Priority: 7
Submitted By: Marius Greuel (greuelm)
Assigned to: Derek (derekc)
Summary: Support ProgIdRef
Initial Comment:
In a scenario where two mutually exclusively installed
components register an identical COM component, the
ProdId definitions clash if the whole Class & ProdId
tables are repeated, as ProgIds are not specific to a
component.
A ProgIdRef element would allow one to reference an
existing definition.
Currently, I don't see a way to generate the Class tables
with the proper default ProdId without the use of
CustomTables.
<Component Id="ansi">
<Class ...>
<ProgId Id="SharedProgId" ... />
</Class ...>
</Component>
<Component Id="unicode">
<Class ...>
<ProgIdRef Id="SharedProgId" />
</Class ...>
</Component>
----------------------------------------------------------------------
Comment By: Derek (derekc)
Date: 2006-04-17 00:53
Message:
Logged In: YES
user_id=518766
This is a good catch. The proposed fix looks like it might
need a slight tweak though. We basically, need to support
multiple versioned progids for a single version-independent
progid. We should not support assigning multiple CLSID to
the same versioned progid.
So we should support something like this:
<Component>
<ProgId Id="unversioned" .../>
<Class ...>
<ProgId="versioned.1" ...>
<ProgIdRef Id="unversioned" />
</ProgId
</Class>
</Component>
<Component>
<Class ...>
<ProgId="versioned.2" ...>
<ProgIdRef Id="unversioned" />
</ProgId
</Class>
</Component>
We should also consider deprecating ProgId under Component
elements (since this relationship doesn't exist in the MSI)
and instead allow a ProgId under Product, Module, and
Fragment for scenarios in which its shared.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=956969&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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
