Yep, Saw that. That was where I first saw how I was doing things a little differently. I actually do Assembly.GetTypes() and looked for any class with a TaskNameAttribute, and use those as my tasks types. It differs from how Project.AddTasks works.
What happens if you have a task (a subclass of Task) without a TaskNameAttribute (really an ElementNameAttribute)? I think the TaskBuilder .ctor needs to check to make sure that taskNameAttribute isn't null before it sets the _taskName class variable. -----Original Message----- Scott Hernandez wrote: [snip] >I've created a simple example that creates XSD Elements for each >TaskNameAttribute and uses the TaskAttributeAttribute as XSD Attributes. >Now I need to finish it up by doing included Elements :) > > cool. Did you look at the code in Element.InitializeAttributes() ?? It scans for included elements to actuall load tasks from the build file Ian _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
