Yes, working and useful code can always find a place in cvs. :) I think there was some question about getting info about tasks and properties and such a while ago. If anyone wants more background I can digup and explain the issues with code attributes, and what info they lack. We have since cleaned up the actual code that used those attributes which make the type info, and code attributes more complete for describing an xml schema, but not quite there. You may also want to look at the nantschema task.
----- Original Message ----- From: "Ian MacLean" <[EMAIL PROTECTED]> To: "Jim" <[EMAIL PROTECTED]> Cc: "'Gert Driesen'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, September 15, 2003 7:14 PM Subject: [NAntC-Dev] Re: Addin > Jim, > I'd say just go for it. There hasn't really been much work done on it > since it was donated by Jayme so there isn't much cvs history to > preserve. My feeling is build it right and we can sort out cvs afterward. > > Ian > > >Hey Guys... > > > >I'm in the process of re-writing the addin for VS.Net. This email > >mainly has to do with how CVS should be handled when I'm finished. > >There are a few files that could keep the same name and continue the > >history, but there are a lot of files that are not part of the existing > >addin code. > > > >So my question is how to go about upgrading what is there. As I said, > >what I am doing is based off Jayme's original work, but for the most > >part, it'll be a re-write of the addin. > > > >Thanks > > > >Jim ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
