Bugs item #1888461, was opened at 2008-02-07 01:37
Message generated for change (Comment added) made by barnson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1888461&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: candle
Group: v3.0
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Rob (rmacfadyen)
Assigned to: Nobody/Anonymous (nobody)
Summary: Class element additional attributes
Initial Comment:
It would be handy if the Class element supported the following attributes:
MiscStatus
ToolboxBitmap32
It would also improve the syntax of the Class element if it supported:
ProgId
VersionIndependentProgID
In combination these would allow for a Class element to handle a broader range
of COM objects (eg. typical GUI components created using ATL).
Instead of:
<Class Id="{someguid}" Context="InprocServer32" Description="Description of
control" ThreadingModel="apartment" Version="1.0" Control="yes"
Programmable="yes" Insertable="yes">
<ProgId Id="Prog.Object.1" Description="Description of control">
<ProgId Id="Prog.Object" Description="Description of control" />
</ProgId>
</Class>
<RegistryValue Root="HKCR" Key="CLSID\{someguid}\MiscStatus\1" Value="12312"
Type="string" Action="write" />
<RegistryValue Root="HKCR" Key="CLSID\{someguid}\ToolboxBitmap32"
Value="[!myobject.dll], 1" Type="string" Action="write" />
You could use:
<Class
Id="{someguid}"
Context="InprocServer32"
Description="Description of control"
ThreadingModel="apartment"
Version="1.0"
Control="yes"
Programmable="yes"
Insertable="yes"
ProgId="Prog.Object.1"
VersionIndependentProgId="Prog.Object"
MiscStatus="12312"
ToolboxBitmap32="[!myobject.dll], 1"
/>
These changes are more than mere cosmetics. The goal is to allow a COM object's
registration to be centralized into a single location in the .wxs file (ie. the
Class element).
Along those lines perhaps a more general solution would be better. Some sort of
<Registeration> child element. This element would work like RegistryValue
and/or RegistryKey. Then whatever registry values required for a COM object
would appear directly beneath its Class element.
Note: If these changes are made then corresponding changes will be needed for
the COM harvestor in heat.
----------------------------------------------------------------------
>Comment By: Bob Arnson (barnson)
Date: 2008-05-30 03:11
Message:
Logged In: YES
user_id=26581
Originator: NO
Good idea but not a bug; please file a feature request.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1888461&group_id=105970
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
