Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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?
NDepend now supports code rule over LINQ query (CQLinq) that is much more more powerful and flexible than CQL (still supported).
What really matters is what kind of refactoring make a code cleaner, according to you. Dozens of new code rules are provided but the real strength is that it has never been easier to write your own code convention and rule.
Here are 5 conventions worth to follow according to me:
I wrote more about my preferences here:
Fighting Fabricated Complexity
Top 5 development practices you should care for