Our test output should probably also indicate the source of the problem - ie 'cl.exe not detected on the current path' or somthing like that.
Ian William E Caputo wrote:
Gert:
However, I agree that we should somehow find a solution for this problem...
What if those tests were marked with the [Ignore] attrbute? That way it will be clear that they are there (as they will show up in the NUnit output as warnings) and then those who wish to run them, can simply unmark them.
Best, Bill
William E. Caputo ThoughtWorks, Inc. -------- A Plan is a list of things that don't happen http://www.twelve71.com/caputo/
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
