Yep, I'm wishing I would have made them attributes of the project element instead of properties. Oopppsss... :)
> -----Original Message----- > From: Tomas Restrepo > > Another way to do this is to establish an event model so that you can > > add an eventTask which will be called for certain things. > > I think this would be a sweet idea, and could be built on top of the > existing project and task runner classes (i don't have the source code > handy, so I can't check right now). Yep, it should be pretty trivial to add the events. From code they could event be cancelable. It would give the option to ignore certain tasks, or types of tasks, or the ability to take over (a cancel and execute your own)... just a thought. Kinda like the OpenDialog in that respect; cancelable. > > Once you had that, it would be a snap to change onsuccess/onfailure so > that all they do is attach event handlers that simply fire off a task, and > it would completely eliminate the issue Robert is seeing (In fact, I'd say > that onsuccess/onfailure should've never been implemented as properties... > too much baggage associated) _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
