To in-charge-type-dudes,

There seems to be a lot of emails about the nUnit2 task not working properly. And generally the reply is a canned "nUnit2 task is not really supported. You are better off using <exec> and the nunit executable"

For the 1.0 release, would it be an idea to remove the nUnit2 task? People are going to keep using it and striking problems unless either it is removed and they can only use <exec> or it is improved to be of releasable nature. I don't think it will matter how may faq entries, warnings, compiler warnings, etc, etc you put up. If someone sees an "nUnit2 task", and they are trying to implement nUnit testing they will jump on it.

Angus.

Reply via email to