Email
Like
Liked ×
Save
Private Content
Embed
Loading embed code…
×
This activity has also been shared with your LinkedIn network
Undo LinkedIn share Settings
We have emailed the verification/download link to "".
Login to your email and click the link to download the file directly.

To request the link at a different email address, update it here. Close
Validation messages. Success message. Fail message.

Check your bulk/spam folders if you can't find our mail.
Loading

Follow

Dev Link2009 Asp Net Mvc Pattern And Ani Patterns Chris Hefley

by Chris Hefley, Working at Bandit Software on Aug 17, 2009

4,013 views

ASP.Net MVC: Patterns and AntiPatterns. Presentation from Devlink 2009, Nashville, TN, Chris Hefley http://indomitablehef.com

ASP.Net MVC: Patterns and AntiPatterns. Presentation from Devlink 2009, Nashville, TN, Chris Hefley http://indomitablehef.com

Statistics

Views

Total Views: 4,013
Views on SlideShare: 3,861
Embed Views: 152

Actions

Likes: 2
Downloads: 65
Comments: 0

5 Embeds 152

http://www.kevinrohrbaugh.com	138
http://www.slideshare.net	9
http://www.linkedin.com	3
http://kr-website.dev	1
http://kevinrohrbaugh.ghost.io	1

Accessibility

View text version

Categories

Technology

Upload Details

Uploaded via SlideShare as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

File a copyright complaint

Hi everyone, thanks for coming. This is ASP.NET MVC: Patterns and AntiPatterns, and I’m Chris Hefley. You’ll often see a talk like this one labeled as “Asp.Net MVC Best Practices”, but I intentionally stayed away from that formulation. I don’t really like the use of the term “Best Practices” most of the time, because it’s usually being used by someone who wants to sound authoritative about something they don’t understand well enough to explain why they feel the way they do about it.These are things I’ve found useful, and of course this is all “in my opinion”, but I’ll do my best to explain why each of the items we’ll cover is considered good or bad. This is not an introduction to ASP.Net MVC, but…since this is the only ASP.Net MVC talk here this year, I’m going to spend exactly one slide on explaining how MVC works, so that any of you are completely new to it may have a chance of remembering some of these things once you do get more familiar with it.
Ok, now on with the show.
When you hear talk about an “Anemic Domain Model”, it’s referring to a domain model that is almost all data and no behavior, such that all the behavior of the system is captured in some other layer, like a service layer or worse, in the presentation layer. That’s bad. An anemic controller, however is Good. Just like it’s a bad idea to put domain logic in your code-behind pages in web forms, it’s not a good idea to fill your controllers with that kind of logic either. Your controller actions should just call methods on some service layer or domain layer class, prepare any view models you are using (more on that later), and render the ViewResult or other ActionResult as needed. Think of them almost like Event handlers. They capture the incoming request, bind to the ViewModel passed back from the view, and pass that model on to another layer for processing.I like to find an illustrative image for these patterns, but when I googled “Skinny Controller, Fat Model” the results I got, while very illustrative of the point, were not really appropriate for display in a public forum.
Why? Because it will cause bugs in your code later. Expensive, hard to find bugs.
And this bit of code leads us right into our next pattern…
Don’t use ViewData[“key”] and don’t explicitly assign ViewData.model = model; Instead, use strongly typed views, and return View(model);For things like ViewData[“ErrorMessage”], create a base class for your ViewModel, that has properties like string ErrorMessage; etc.
Don’t use ViewData[“key”] and don’t explicitly assign ViewData.model = model; Instead, use strongly typed views, and return View(model);For things like ViewData[“ErrorMessage”], create a base class for your ViewModel, that has properties like string ErrorMessage; etc.
Don’t use ViewData[“key”] and don’t explicitly assign ViewData.model = model; Instead, use strongly typed views, and return View(model);For things like ViewData[“ErrorMessage”], create a base class for your ViewModel, that has properties like string ErrorMessage; etc.
User interface segregation principle insteadShow code: IUserContextShow Code: one-off-view-model
MvcContrib comes with ControllerFactories for several of the most popular IOC containers
MvcContrib comes with ControllerFactories for several of the most popular IOC containers
Show Ktransaction attribute

2 Likes

J Wynia, Software Developer at Pragmapool, Inc. 4 years ago
Jungchan Hsieh, Application Developer at market 4 years ago

Dev Link2009 Asp Net Mvc Pattern And Ani Patterns Chris Hefley Presentation Transcript

ASP.Net MVC : Patterns and AntiPatterns
Chris Hefley, Bandit Software
Blog: http://indomitablehef.com
Email: [email protected]
Twitter: @indomitablehef
Model View Controller
ASP.Net ISAPI filter
HttpModules and HttpHandlers
HttpRequest
Request
Routed
To
Retrieve Data from
Some Class
Some Model
System.Web.UI.Page
System.Web.Mvc.Controller
Render
Some View
Anemic Controller
“Skinny Controller, Fat Model”
GOOD
BAD
Magic Strings
ASP.Net MVC Magic Strings
Banishing Magic Strings: Views
Instead of:
Use:
Banishing Magic Strings: Controllers
Banishing Magic Strings: Controllers
GOOD
One Action, One View
Instead of:
One Action, One View
Do this:
GOOD
View Models
BAD
ViewData Dictionary
GOOD
ViewModel Base Class
Instead of ViewData Dictionary:
ViewModel Base Class
Instead:
w00t!
Use MVC Contrib
BAD
JavaScript in Views
If you must:
More goodness from MVC Contrib:
BAD
Branching Logic in Views
Don’t do this:
Or even this:
Branching Logic in Views
Branching Logic in Views
BAD
HttpContext
GOOD
IOC Container
IOC Container
GOOD
Extensions to HtmlHelper
BAD
DataBinding to Domain Object
GOOD
Custom ActionResult
Miscellaneous
Use Html.Encode
jQuery!
Use AcceptVerbs Attribute on Controller Methods (POST for those that modify Data)
Use ASP.Net MVC to create REST-ful APIs
Extension Methods to UrlHelper
Make good use of ActionFilters
GOOD
After-Market Parts
Spark View Engine
Sparkviewengine.com
S#arp Architecture
Questions?
Chris Hefley, Bandit Software
Blog: http://indomitablehef.com
Email: [email protected]
Twitter: @indomitablehef