[textile].NET Developer (and friend) "Joe Field":http://joefield.mysite4now.com/blogs/blog/ sent me this link... "Visual Studio Add-Ins Every Developer Should Download Now":http://msdn.microsoft.com/msdnmag/issues/05/12/VisualStudioAddins/default.aspx I already knew about "Test Driven .NET":http://www.testdriven.net/ but what is going to come in handy for me right now is "GhostDoc":http://www.roland-weigelt.de/ghostdoc since I am documenting an API (that Joe and I developed) for a client before I move focus onto another project with a new client.

The goal of GhostDoc is to automate the tedious parts of writing XML comments by looking at the name of your class or method, as well as any parameters, and making an educated guess as to how the documentation should appear based on recommended naming conventions. This is not a replacement for writing thorough documentation of your business rules and providing examples, but it will automate the mindless part of your documentation generation.

[textile]Looks interesting... Will have to investigate this tool...

"MailFrame NUnit TestRunner":http://www.mailframe.net/Products/TestRunner/2005/

I like the look of the visual integration with the Visual Studio editor...

[textile]While helping someone get started with evaluating "SWExplorerAutomation":http://home.comcast.net/~furmana/SWIEAutomation.htm (I'll call it SEA if you don't mind) on a client's site, we encountered an error almost as soon as we tried to use it... but it turned out that it had nothing to do with the tool and everything to do with a bug in an MS Security Patch... "read on to find out more":http://www.testingreflections.com/node/view/2592

At first glance, building and deploying applications seem simple enough. But in fact, difficult releases without any confidence or processes backing them are very common. Integration and management of a new deployment can be laborious and fraught with risk. So as team size and volume of projects grow, management becomes more difficult and risk more pronounced.

This book is a guide to the implementation of good processes in a .NET environment. Author Marc Holmes focuses on actual implementation, and details patterns and anti-patterns to watch out for. He also provides a practical and in-depth look at NAnt and CruiseControl.NET, and solutions to common problem scenarios.

Ayende has announced that he's released Rhino.Mocks v. 2.0: his own version of what he'd like in a Mock Object framework. I haven't yet got a chance to try it out, but it certainly sounds interesting!

"Rhino.Mocks is an attempt to create easier way to build and use mock objects and allow better refactoring support from the current tools. It's a hybrid approach between the pure Record/Replay of EasyMock.Net's model and NMock's expectation based model. Rhino.Mocks originated from EasyMock.Net and attempt to improve on their model to create easy to use and power mocking framework. It's free for use and modification for free and commercial software.

I created a Setup.aspx file that would allow me to make requests to it and pass in a static method that I wanted to call, and as a result, any code that ran inside of it would run inside the web’s application domain and have access to the Session and HttpContext.

Author: Robin Curry
Published: June 27, 2005

A dynamic mock object framework for the .Net platform. Its purpose is to ease testing by allowing the developer to create mock implementations of custom objects and verify the interactions using unit testing.

Rhino.Mocks is an attempt to create easier way to build and use mock objects and allow better refactoring support from the current tools. It's a hybrid approach between the pure R

While unfamiliar to many developers, Continuous Integration is not a new concept at Microsoft, as is evident by Steve McConnell's observation. Consequently, in this second installment of a two-part article, I examine the setup of a version-control system and configuration of a Continuous Integration tool that runs off of the version-control system in the .NET environment. I then integrate these tools into the build process to test for conformance with the Microsoft .NET Framework Design Guidelines, and finally address the issue of code-coverage testing.