Yes, I think the core of the code should probably be written as a task. The task should be able to do the things you've described, like save the xsd.
The only difference will be how the task list is created; which determines which tasks are defined in XSD. We also have the option here of only checking the types we know about. Since the build file project element can contain any number of child elements, and in no specific order, there really isn't a high level of granularity for checking anyway. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Gerry Shaw Sent: Monday, April 15, 2002 5:18 PM To: [EMAIL PROTECTED] Subject: RE: [nant-dev] XML Schema Def (XSD) I suggested it as a task for the following reasons: * You can't auto build a schema until are the tasks are loaded. * The build file might contain some <taskdef> tasks that load additional tasks from locations nant doesn't know about. * Tasks have access to the XmlDocument object that represents the build file. * You might want to do some really funky stuff in the future, exporting the .xsd is an obvious feature. * No special code needs to change inside nant. _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
