Comment 2 for bug 1098766

I think you first point would be a great reason to provide an attribute call AssemblyTearDown and AssemblySetup.

I am not sure why you are saying it shouldn't involve searching all methods of all classes to find the proper methods. I didn't suggest such an awful thing. Not sure why it would, that is the purpose of the attributes I would think, and it can require that a class has a TestFixture attribute to make it simpler.

Basically what I am asking for is for how AssemblyCleanup works in MSTest. All the rules/restricts I mention are how it works in MSTest and it seems a safe approach and made sense.

I will look at how you suggest as it will work as it would be better than the hack I had to do to port this from an MSTest project to NUnit that had used AssemblyCleanup.

Thanks for the HOW TO and I hope you make this functionality a little more obvious and intuitive in the future.