Bugs item #1291401, was opened at 2005-09-14 14:35
Message generated for change (Settings changed) made by robmen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1291401&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: documentation
Group: v2.0
>Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: requim (requim)
Assigned to: Derek (derekc)
Summary: ClassContextType
Initial Comment:
2 Items:
1st, the manual has a dead link to ClassContextType, so
I had to look in the XSD to find the definition.
2nd, a request Can we change the value from
InprocServer and InprocServer32 to InProcServer and
InProcServer32. I only ask because tallow parses it
out as InProcServer32 and everywhere else I've looked
I've seen it written out that way.
Here's the snippet from the latest XSD with the current
definitions:
<xs:simpleType name="ClassContextType">
<xs:annotation><xs:documentation>Enum type for the
Class element's Context attribute
list.</xs:documentation></xs:annotation>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="LocalServer"/>
<xs:enumeration value="LocalServer32"/>
<xs:enumeration value="InprocServer"/>
<xs:enumeration value="InprocServer32"/>
</xs:restriction>
</xs:simpleType>
Thanks!
Jon
----------------------------------------------------------------------
Comment By: Derek (derekc)
Date: 2005-11-09 00:23
Message:
Logged In: YES
user_id=518766
This should be fixed in the next drop.
----------------------------------------------------------------------
Comment By: requim (requim)
Date: 2005-09-15 11:44
Message:
Logged In: YES
user_id=1317338
Disregard the 2nd item. I must have done a search and
replace using InProcServer32 instead of InprocServer32 and
mistook it for being generated by tallow. I was only
looking at the output generated and must have done the
search and replace several weeks ago and forgotten all about it.
My mistake.
----------------------------------------------------------------------
Comment By: Derek (derekc)
Date: 2005-09-15 11:20
Message:
Logged In: YES
user_id=518766
The first issue is defintely a bug that should be fixed.
I'm not sure I understand the justification for the second
part of the bug - why is the casing of InprocServer* a problem?
Where did this alternative casing come from? From what I can
see in the MSDN documentation WiX is using the correct casing:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/com/html/4edbbd9d-7ea1-4476-aee7-eaf30e54db8d.asp
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1291401&group_id=105970
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
