> Another solution is by using an <import> task that replaces the <taskdef> > task. It would be used like this: > > <import assembly="NAnt.DotNetTasks.dll" prefix="dotnet-"/> > > You would then use the tasks from this assembly as follows: > <dotnet-csc/> > > Omitting the prefix attribute just brings the tasks into the default > namespace. The tasks in NAnt.Core would always be in the default namespace. > Consider them "reserved" words. >
This makes a hell of alot of sense. I've wondered why the original ant project didn't do something like this. This also brings up the possibility of writing an XML Schema for your task, and validating against it in InitializeTask() since all the elements below the task could (potentially) be prefixed with the same namespace. If you were allowing filesets, there could be a schema for regular NAnt elements (project/target/property/fileset) that you could extend types of, or just include as is. -Jayme ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
