[ wix-Feature Requests-1245099 ] CodeDOM: XXXRef elements should have a ResolveReference() me

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[ wix-Feature Requests-1245099 ] CodeDOM: XXXRef elements should have a ResolveReference() me

SourceForge.net
Feature Requests item #1245099, was opened at 2005-07-26 03:04
Message generated for change (Comment added) made by rgustin
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1245099&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: Closed
Priority: 5
Submitted By: Frederik Carlier (fcarlier)
>Assigned to: Nobody/Anonymous (nobody)
Summary: CodeDOM: XXXRef elements should have a ResolveReference() me

Initial Comment:
For example, DirectoryRef.ResolveReference() would
return the referenced Directory, or null.

----------------------------------------------------------------------

>Comment By: Reid Gustin (rgustin)
Date: 2005-10-12 11:55

Message:
Logged In: YES
user_id=1011559

XsdGen gets used in a number of places, not just in WiX. The
ClickThrough project Rob, Derek and I are working on also
uses it, for example.

I'm saying that XsdGen will not be WiX specific. If you'd like
to build something on top of the CodeDom that has WiX-
specific knowledge, that seems very reasonable, but it won't
be coded straight in. Please feel free to open a separate
feature request for that.

----------------------------------------------------------------------

Comment By: Frederik Carlier (fcarlier)
Date: 2005-10-12 03:21

Message:
Logged In: YES
user_id=1149415

I don't understand this.

XsdGen lives in WiX, so enhancing it to work with WiX would
be a feature, no? If XsdGen is supposed to be more general,
well, what more is it than recreating the tools that already live
in .NET Framework?

Besides, this is a feature that people that, for example,
implement editors will use, so the feature has a reason to live
inside WiX. There is a real usage scenario for this.

If you want to keep XsdGen more general, okay, but why not
using the XsdGen as a base for a more 'WiX-specific' utlity?

In short: this is a feature that has a place in WiX. (IMHO)

----------------------------------------------------------------------

Comment By: Reid Gustin (rgustin)
Date: 2005-10-11 23:59

Message:
Logged In: YES
user_id=1011559

This would end up being heavily WiX-specific. The XsdGen is
more general purpose than that, so I'd like to keep the WiX-
specific concepts out of it.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1245099&group_id=105970


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
WiX-devs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-devs