Just uploaded new code drop, with a few minor fixes and NUnit support. Now you can run tests in both environments - VS Test or NUnit. There are two test projects in the solution for each option plus conditional attribute renaming in source code (test are
shared between the two projects).
After doing all this, checking in, getting all back from codeplex I found a problem. I usually update the zip on Downloads page right after I do the checkin. I download the sources back, open VS, remove source control bindings (to make things easier for
those who will use the downloads), build, run unit tests, etc. It turns out, after I removed bindings and disconnected from TFS (codeplex), VS Tests stopped working. Attempt to run the test project pops up a box with a message "The target of invocation
had thrown an exception". If you experience the same effect, here's the situation.
It turned out it is a known problem - read the following post, and there are several workarounds there:
what worked for me is simply reconnecting with TFS (without binding the project) - after reconnection it started working. Alternatively you can consider deleting the registry key as described.
On another theme, I'm preparing to move to VS 2010/.NET 4. I'm planning to make project runnable in both environments for a while. In the current version you'll notice that I added suffix "2008" to project and solution files. Next time there will
be 2010 versions.