> aren't we phasing out taskdef in favour of loading tasks from > assembiles > in a given directory - reinforces the above
Phasing out taskdef in favor of forcing tasks to be in a specific folder seems like a good way around this. If we go with the .config file you could specify additional folders for nant to probe beyond the folder where nant.core.dll lives and maybe a tasks subfolder. This would get rid of the problem of not knowing all the tasks at build start. > Why not have the element class have a default implementation based on > the Attributes and if a task chooses to override this for > some reason it can. Yes, this seems like a good design. > Or are you thinking of imposing the order of the document instance in > the schema ? No, that seems like a lot of work for very little additional error checking. I mainly want a .xsd so when I go and type in a build file and type: "<csc " I get a popup list of all the attributes for the csc task and when I close the tag with <csc> and type "<" I get another popup list of all the child elements that can exist inside the <csc> task (ie, <sources>, <references>, etc...) Secondary I'd like nant to be able to throw a build exception (right at the start if possible, but during build is acceptable) if I have something like: <nunit haltOnError="true"/> when it should have been <nunit haltonerror="true"/> _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
