Unit Testing with Visual Studio 2005
Strengthening Visual Studio Unit Tests, MSDN Magazine, March 2006
Write Unit Tests With VSTS, Visual Studio Magazine, January 2006
Unit Testing and Generating Source Code for Unit Test Frameworks, September 2005
Unit Testing in General
Presentation: Net Objectives The Case For Unit Testing Streamzine
You found another good source of information on Unit Testing in VS 2005? Post it as comment!
[Excerpt from my more complete list on www.dotnet-online.com/teamsystem/]
Found as a workaround for Forms designer issues on the MSDN Product Feedback Center:
Workaround Steps:
1) Go to your project directory, list the hidden files and look for one ending in .suo. Delete that file. This file just tracks what you had open, so you won't lose anything important.
2) You should now be able to start VS. Start two instances of VS, attach one to the other (Debug >> Processes >> devenv.exe).
3) Choose Exceptions >> CLR Exceptions >> Break when exception is thrown
4) Go the the other version of VS (the one that's being debugged) and open your form.You'll start breaking on exceptions. Hit continue until you see an exception of type ArgumentException.Look at the stack, and post it here. If it's something in your code you can fix it but in either case the designer shouldn't crash there, so the stack will tell us where we're letting an exception sneak through. We did a bunch of work to catch all of those, but there's a lot of possible nooks and crannies.