Comments on: Project-wide controller survey through reflection

By: drozzy

drozzy — Tue, 26 May 2009 15:22:12 +0000

Just gota love the microsoft convention of naming obvious things in obvious ways:
Controller AccountController;

Why not go all the way and call a string for what it is?
String first_name_string;

By: bogardj

bogardj — Fri, 15 May 2009 12:24:04 +0000

@Jeff

That’s something I thought about…but since this code lives in an explicit unit test (my favorite sandbox), it’s only a few keystrokes away inside VS.

@Depaulo

Oh yeah, we have another test that goes through our actions and finds “bad” ones. You might be able to get that too with the Type.IsAbstract and doing another Where.

By: Depaulo

Depaulo — Fri, 15 May 2009 09:31:58 +0000

Awesome! A problem we get sometimes is that when a domain class is made abstract, suddenly actions fail as the model binder can no longer instantiate the class. I have used your code here to create a test which runs through all our action method parameter types and try to instantiate them. Now we will never have the problem again! Hurrah!

By: Garry Shutler

Garry Shutler — Fri, 15 May 2009 07:41:40 +0000

I like it. What would be even cooler (haven’t worked out in my head how you’d achieve it) would be if you could generate the URL for each of the actions as well.

By: Jeff Doolittle

Jeff Doolittle — Fri, 15 May 2009 05:46:37 +0000

Might be worth taking a look at NDepend.

By: Rob Scott

Rob Scott — Fri, 15 May 2009 03:08:27 +0000

Nice.