views:

100

answers:

1

I'm working on a brown-field project that was initially developed for .NET 1.1, and subsequently was retro-fitted to .NET 2.0, with a smattering of .NET 3.5

I'm curious what kind of metrics to use to begin finding optimization and modernization inflection points.

Are there any good CQL queries that anyone has found useful in cleaning up and refactoring 'legacy' .NET code?

+5  A: 

Maybe you can first forbid usage of .NET 1.1 collection, there are a few CQL default rules for that in the CQL group: .NET framework Usage > System.Collection

But what really matters is what kind of refactoring make a code clean, according to you. I wrote about my preferences here:

Fighting Fabricated Complexity

Top 5 development practices you should care for

Patrick Smacchia - NDepend dev
Fantastic I'll upvote in about 6 hours after my upvote cap limit has expired :)
John Weldon