Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at
NDepend ... the Shortest Review Ever

A long while ago I got a licence for NDepend ... I had used it previously but only on the trial version, where it had proved very useful in giving me a some pretty graphs that made sense to managment when my words did not.

I haven't actually got around to using it until this morning, when I thought I would run it over our current project to see where we were at. There isn't a hell of a lot of code in the project, so I wasn't expecting too many surprises - and largely I didn't receive many.

I was pleased to see our assembly dependencies were the right way around, and very pleased to see they were very near the centre line on the "Abstractness vs Instability" chart.

The only very mild surprise was to see this flagged up in multiple CQL checks:

RegisterforUpdates(String, String, String, String, String, String, String, String, String, String, String, String, String, String, String, String, String)

Obviously there is something wrong here ... and a quick word with the developer who wrote this established that he didn't know about the Binding Helpers in ASP.NET MVC so had passed every form field back into the controller via the parameter list. A quick hyperlink to him of Rob Conery's excellent tutorials on ASP.NET MVC and we have a much nicer method on the controller.

One small win for NDepend ... I look forward to many more as time goes on!


Posted 08-19-2008 9:14 AM by Jak Charlton
Filed under: , ,



Kyle Baley wrote re: NDepend ... the Shortest Review Ever
on 08-19-2008 9:39 AM

Re: Binding Helpers. I've also been using the Deserialize attribute from MvcContrib to pass objects to controllers. I found it makes the controllers easier to test.

Jak Charlton wrote re: NDepend ... the Shortest Review Ever
on 08-20-2008 3:18 AM

Interesting point ... had of course forgotten the "how do I test this annoying method on the controller now that it uses Request.Form" aspect ...

I took a brief look at the MVCContrib bits here but didn't like it much, have been trying to stick to vanilla MVC for the moment as it is still in flux.

However I think we now need to look at this ... though we aren't unit testing controllers at the moment (or anything else for that matter) as the team is too inexperienced to bring in unit testing with the stupidly short deadline they have to deliver something, and to have them remain productive.

About The CodeBetter.Com Blog Network
CodeBetter.Com FAQ

Our Mission

Advertisers should contact Brendan

Google Reader or Homepage Latest Items
Add to My Yahoo!
Subscribe with Bloglines
Subscribe in NewsGator Online
Subscribe with myFeedster
Add to My AOL
Furl Latest Items
Subscribe in Rojo

Member Projects
DimeCasts.Net - Derik Whittaker

Friends of
Red-Gate Tools For SQL and .NET


SmartInspect .NET Logging
NGEDIT: ViEmu and Codekana
NHibernate Profiler
Balsamiq Mockups
JetBrains - ReSharper
Web Sequence Diagrams
Ducksboard<-- NEW Friend!


Site Copyright © 2007 CodeBetter.Com
Content Copyright Individual Bloggers


Community Server (Commercial Edition)