Vicky, it's not about running NUnit tests in VS 2012 (that seems to work), it's about running them on TFS 2012 during CI builds. Apparently there are known issues with the NUnit Test Runner Extension (http://visualstudiogallery.msdn.microsoft.com/6ab922d0-21c0-4f06-ab5f-4ecd1fe7175d) on 64-bit machines. But even after following the steps documented in several articles (http://www.codewrecks.com/blog/index.php/2012/03/05/running-nunit-and-xunit-tests-in-tfs11-build/, http://blog.accentient.com/2012/04/30/RunningNUnitInATFS11BuildOn64BitServer.aspx), I still can't get the "custom assemblies" to be picked up by TFS 2012.
I've tried queuing builds from both VS 2010 and 2012, but nether work. And even after I point the Build Controller to the custom assmblies folder and I go to edit the build definition, I get a "No custom assemblies found in reference folder" message (or something like that) in VS 2012, which seems to me to indicate that TFS 2012 is not seeing those NUnit extensions in my custom assblies folder.
Thanks,
--Henry
