"The Issue, in which Dylan gets bit in the ass by a legacy database I'm building some message-oriented-middleware (MOM?) for a 3rd party vendor product. The database has evolved over many years and has all of the quirks that you might expect of such a system: primary keys that are implied but not made explicit with constraints, relationships that are implied but not explicit, columns that are not nullable in the business logic but are nullable in the tables, etc. I'm not knocking the vendor: I am keenly aware that keeping a multipurpose database absolutely clean of cruft is a tough challenge indeed. But it does make for some really tough integration points. My major challenge over the past week has been auditing. The vendor system makes very heavy use of sprocs and embeds the creation of the audit trail in those sprocs rather than using what, to my mind, is the more obvious approach of triggers."

"My workplace has been having issues with VS2010 picking up old assemblies since we have been using VS2010 on a complex services solution. The issue usually pops up when executing test runs with the built in support for MSTest. This occasionally happened in VS2008 but is much more prevalent in 2010. The scenario seems to be that somewhere between the IDE and MSTest is picking up assemblies from prior TestResults directories if the assembly can't be found in bin\Debug or bin\Release directories. This means that the normal clean operation under the build menu is not sufficient to get rid of this problem. Enter the sledgehammer. I wrote a little utility that will recursively go through each bin, obj and TestResults folder under the solution path and delete everything it can (including read-only files). Any exceptions encountered will be output to the console. The code itself is really simple."

"Closure Inspector is an extension to Firebug, the Firefox debugger extension. Closure Inspector adds three powerful features to Firebug: source mapping, improved stack trace display, and unit test integration. This document describes how to install and use Closure Inspector."

" The Closure Compiler is a tool for making JavaScript download and run faster. It is a true compiler for JavaScript. Instead of compiling from a source language to machine code, it compiles from JavaScript to better JavaScript. It parses your JavaScript, analyzes it, removes dead code and rewrites and minimizes what's left. It also checks syntax, variable references, and types, and warns about common JavaScript pitfalls. "

" Raphaël is a small JavaScript library that should simplify your work with vector graphics on the web. If you want to create your own specific chart or image crop and rotate widget, for example, you can achieve it simply and easily with this library. "

"JavaScript Outlining * Outlines JavaScript codeblock regions for the code placed between { }. Both places on a new line. * Outlines custom regions defined by: o //#region - //#endregion o //#> - //#< CSS Outlining * Outlines JavaScript codeblock regions for the code placed between { }. Both places on a new line. * Outlines custom regions defined by: o /#region/ - /#endregion/ o /#>/ - /#

" Castle DynamicProxy is a library for generating lightweight .NET proxies on the fly at runtime. Proxy objects allow calls to members of an object to be intercepted without modifying the code of the class. Both classes and interfaces can be proxied, however only virtual members can be intercepted. "

"Unity 1.2 is about to be released anytime now, and one of the exciting new features is that the core interception technology from the Policy Injection Application Block has been moved to Unity. This allows one to do AOP with Unity without the need for Enterprise Library and the Policy Injection Application Block."

"I couldn't find an example of doing AOP Method Interception using Ninject and Castle's DynamicProxy2 or LinFu DynamicProxy, so I consulted Ninject's Unit Tests and created my own sample. In the sample shown below, I will be using Castle's DynamicProxy2, but quite honestly I think you can use Linfu DynamicProxy by just swapping out the DynamicProxy2Module for the LinfuModule in the code below as well as referencing the Ninject.Integration.LinFu Assembly as opposed to the Ninject.Integration.DynamicProxy2 Assembly. By the way, there are some really good CodeProject article's on Linfu that I mentioned on PnPGuidance: LinFu Articles on CodeProject Well-Worth Reading."