Home/ Questions/Q 31439
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T13:36:18+00:00

So I’m embarking on an ASP.NET MVC project and while the experience has been

  • 0

So I’m embarking on an ASP.NET MVC project and while the experience has been a good one overall, I’m not quite as pleased with the spaghetti mess that my controllers have become. I’ve looked around online (CodeCampServer, etc…) and they all seem to suffer the same issue wherein controller methods violate SRP (single responsibility principle) pretty consistently – such as a controller method that simply renders the view if the request is a GET but updates the model if it’s a POST. Now I’ve got controller methods responsible for multiple logical routes throughout the application – say it checks for which button was clicked on the form and acts accordingly. I could redirect each button click to a different form action using JavaScript, but something doesn’t feel right there either… The other big issue is the proliferation of magic strings - ViewData['foo'] = blah; Long story short, how do you guys structure your controller logic? One giant model object per view? Lots of little controller methods and JavaScript is the router? My goal is maintainable code – as features get piled on I’m starting to slide down that slippery slope…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. ASP.NET Preview 5 (available on CodePlex) has an answer for this: the [AcceptVerbs] attribute. Phil Haack has a blog post discussion how it’s used.

    As for the view data magic key question, it’s an interesting problem. If you think of a view as being a bunch of semi-independent components (especially in light of the new partial view support), then making a strongly-typed model becomes less ideal, as the several pieces of the view should be relatively independent of one another.

    • 0