Why dependency on empty .nunit file?

Topics: Developer Forum
Jun 5, 2008 at 5:38 PM

I was wondering why there is a dependency on an empty "*.nunit" file? Is this the metric used to determine the project(s) to load up with the addin?

If that is the case what about using an assembly attribute in the projects we would like to make visible to the built in MS testing framework.

Any thoughts?
Jun 12, 2008 at 9:44 AM
VS uses this file to know if it should execute NUnitForVS. This is a limitation of MS testing framework. There are two kind of test "parsers". First one uses file to save test lists or some other information. Second one makes parsing of tests on the fly. MS uses the second parser. Unfortunately it is internal and undocumented. That is why I use file based parser. VS gives this file so we could load the tests, but instead I look in which project is this file in and parse this assembly for tests.
Jun 21, 2008 at 4:34 PM
*.nunit is not needed anymore
Jun 23, 2008 at 10:34 PM
Fantastic Thanks...