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.
But now when I think about how users are going to want to use it I can't help but think of it just doing the right thing and if it doesn't you would just want to: "nant -set:validate=false" rather than change your build file. So that said if you can write a class/method that can take the a Project object, the XmlDocument for the build file (from the project) and validate it we could insert it right after all global project tasks have executed (to load external tasks) but before any targets get called. It might also be possible to do the validation right at the start (before) any project level tasks are executed and just not validate tasks inside targets - not sure if that is possible. I didn't really mean to write this much... Oh yeah, it would also be great to have it output the .xsd file so people can use it when writing the buildfile in VS.NET to get the popup's. _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
