What's the Right Number of Assemblies/Libraries?

Deciding how to physically partition up your application isn't a .NET specific topic, but I'll use the word "Assemblies" and use .NET terminology since we work largely in .NET.

What's the right number of assemblies? When do you split up functionality into another assembly? Should you use ILMerge to make a single über-assembly? Perhaps one class or one namespace should be inside each assembly?

Here's my thinking...organized very simply.

Link to full item

Using TortoiseSVN with Team Foundation Server

This is a new and very interesting project at CodePlex. This bridge allows clients (such as TortoiseSVN) work against a TFS server. This is a group of developers CodePlex itself because of the popularity of clients. The bridge works at the protocol, making SVN protocol TFS protocol and vice versa. The development is in its infancy and it is monitored.
Link

New ASP.NET AJAX Control Toolkit Release

The ASP.NET AJAX Control Toolkit is a shared-source community project consisting of samples and components that make it easier than ever to work with AJAX-enabled controls and extenders. The Control Toolkit provides both ready-to-run samples and a powerful SDK to simplify creating custom ASP.NET AJAX controls and extenders. Make sure you install ASP.NET AJAX 1.0 first!

Download Page

Thanks to ScottGu's Blog

Code snippet: QueryString Properties.

Snippet Detail and Download

IDisposable – 1, 2, 3, …

How and Why read here

Tutorials: "Working with Data in ASP.NET 2.0" - Caching

Link to 4 tutorials available

Thanks to Scott on Writing

Enterprise Library 3.1 is released

Download page

Debugging Stored Procedures in Visual Studio 2005

Debugging SQL Server 2005 Stored Procedures in Visual Studio