StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMVC vs Dependency Injection
text
Body
copied!<p><strong>Can anyone summarize or bulleted list the types of things that go in each layer, and what layers are there in an MVC type design if you account for Dependency Injection?</strong></p> <p>I haven't found any clean diagrams that help me figure out where or try to go more in detail without writing an entire book. </p> <p>I've been doing windows forms apps (including the sql server database design) for 3 years now as my sole function at work , with no one more experienced over me. I have been trying to break things apart into clean layers as much as I can figure my way through on my own based on presentation, business, database. </p> <p>However based on reading the samples of <a href="http://www.manning.com/seemann/" rel="nofollow noreferrer">Dependency Injection in .net</a> it appears that the business logic should be the heart of the application with a separate layer that points to the specific database implementation. So then the ui goes in the presentation layer, controller just provides an abstraction/mapping layer to what the ui is allowed to do in the model layer, the business logic goes in the model layer, and the database/linq-to-sql goes in the database layer. Where everything can depend on the model layer, but it should depend on nothing. </p> <p>To enable you to move the heart from X type to:</p> <ul> <li>Windows forms</li> <li>Asp.net</li> <li>Asp.net MVC</li> <li>Silverlight</li> <li>Anything else</li> </ul> <p>right? <strong>Would a 4 layer/project approach cover this type of thing? I suppose it would be 5 if you add a TDD layer.</strong></p> <p>I'm not averse to reading books, but I have plenty to read ( 3 at home, 1 at work, 3 ordered, 1 for college) already that are quite thick. Both of these approaches have resounding supporters but seem to conflict on overall design. </p> <ul> <li>Extreme programming</li> <li>windows forms in action</li> <li>The productive programmer(75% done)</li> <li>User interface design for programmers (90% done)</li> <li><a href="http://rads.stackoverflow.com/amzn/click/0321545613" rel="nofollow noreferrer">Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries (2nd Edition)</a> - at work that I got from code camp</li> <li>The Art of Unit Testing - <a href="http://www.manning.com/osherove/" rel="nofollow noreferrer">The Art of Unit Testing</a> with Examples in .NET Roy Osherove</li> <li>Operating systems concepts with java - for a master's in computer science class</li> <li>C# in depth(not release yet)</li> <li>Functional Programming for the real world(not released yet)</li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload