Comment 2 for bug 1094245

Revision history for this message
Matthias Kläy (matthias-klaey) wrote :

Hi Charlie,

Thanks for the detailed response! Aiming for NUnit 3.0 is perfectly fine, I totally understand that it makes little sense to still do significant work in 2.x. Something like [Include] and [Exclude] in 3.0 would fulfill my requirements. First I thought that the category attribute could include/exclude itself based on some condition. But giving it a second thought made me conclude that [Include] and [Exclude] must be something in addition / on top of the current [Category] infrastructure. But thinking about it again, having some logic right in the category attribute would be an obvious and compact solution. I'm sure you'll find the best approach to implement this feature.

Regarding the issues with 2.6.x:
A couple of weeks ago I simply uninstalled 2.5.10 and installed 2.6.2 and ran my tests. But that didn't work with .NET 3.5 and VS2008. I cannot remember the error details, but I guess it's just something minor. I didn't want to bother looking into the issue in more detail since I am about finalizing a version of my software and am trying to focus on that. But some time early in 2013 I will upgrade to 2.6.x. If it's an issue I cannot solve I will of course report it to you.

Best regards,
Matthias