http://blogs.msdn.com/ploeh/archive/2006/09/18/test-driven-development-with-test-lists.aspxFor most of the time, I write code using the test-driven development methodology. This means that I write a bit of code, run a suite of tests, write a bit more code, run some more tests, etc. For this reason, I need unit testing to be an integrated parten-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/ploeh/archive/2006/09/18/test-driven-development-with-test-lists.aspx#761856Tue, 19 Sep 2006 14:07:04 GMT91d46819-8472-40ad-a661-2c78acb4018c:761856MarkCan you provide more details of how you setup VS to work with NUnit?http://blogs.msdn.com/ploeh/archive/2006/09/18/test-driven-development-with-test-lists.aspx#761952Tue, 19 Sep 2006 15:37:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:761952Team System NewsGrant Holliday on OzTFS.com Launched. <br> <br>Buck Hodges on VC API: CheckIn() may return 0. <br> <br>Martin Woodward...http://blogs.msdn.com/ploeh/archive/2006/09/18/test-driven-development-with-test-lists.aspx#763402Wed, 20 Sep 2006 11:31:38 GMT91d46819-8472-40ad-a661-2c78acb4018c:763402ploehHi Mark <br> <br>Setting up Visual Studio to work with NUnit is pretty straightforward: Open the project properties for the test project and go the debugging options. Here, you should change the debugging options to launch an external program and specify either the NUnit GUI or console (depending on your personal preferences). You'll also need to supply a command line parameter to NUnit to specify which test library should be loaded (refer to the NUnit documentation for the exact syntax). After doing this, pressing F5 will launch the NUnit executable with your test library loaded and the debugger attached. <br> <br>Some people like to use a Visual Studio add-in called Test-Driven.NET, which will also provide some integration between Visual Studio and NUnit, but I always like my own solution better, as it was simple and always worked.