I recently got the chance to learn about a technology that has interested me for quite some time: SQL dependencies.  The premise of my encounter with SqlDependency was to create a smarter cache.  The project I'm currently working on was employing a sliding expiration policy to invalidate the contents of a cache of database lookup values and I proposed some research be conducted into using SQL dependencies to automatically invalidate the cache items when the corresponding database contents were changed.  I had experimented with the SQL dependency classes when .NET 2.0 was first released using a test SQL 2000 database.  The example I was...

I ran into an interesting issue yesterday while adding log4net to a project that was using NDoc as part of its build process. The project is using Team System for both source control and builds, and is using NDoc 2 Alpha 3 to generate code documentation files as part of the build. A common tools folder exists as part of the source control tree that is copied to the build server during the build process and used as a reference point for common libraries throughout the solution. This approach has been successful for me in the past...