Last night attended my first Forth Worth .NET User's Group meeting.  One thing living in DFW is that I have three solid .NET user groups here.  I've previously attended both the North Dallas and Dallas .NET user groups.

Tim Rayburn, NUnit contributor,  did a quality presentation on TDD with .NET and NUnit. 

I wanted to attend this meeting as "sanity check" on how I was implementing TDD.  I've only used TDD on two smaller projects thus far and I don't work with developers who use TDD.  I don't really have a good frame of reference other than books; sometimes its just nice to see how it is done.

Tim went into the background of TDD and things that I've read before.  It was still good especially for those not really that familiar with it at all and good refresher for myself.  What I liked most was his open dialogue with the group.  He took lots of questions and demonstrating his answers within the demo.  Again, just good to see how it's done sometimes.  In large groups like that I'm usually a quiet guy who doesn't speak up but last night I actually asked two questions and made one comment.  Woohoo. 

I now have some answers to work with and an answer to my main question:  What is a good strategy to structure your projects/solution to keep the test class with your code so it doesn't get lost but it is compiled as a separate DLL.  Answer:  In your solution, for each code project have one test project.  This way you can reference your code from your test project for the tests and they get complied as different DLLs.  Not to mention you don't have to mess with the access level of your methods in your code.

Good stuff!