The document discusses architecting, testing, and developing an MVC application. It covers the speaker's architecture which uses a 3-tier (presentation, business logic, data) separation with projects for each layer. Benefits include reusability, testability, and avoiding references issues. The speaker recommends using common libraries like Entity Framework, Ninject, jQuery, and NUnit and provides a demo of unit testing a controller and project structure. Questions are welcomed via social media.

1. Architecting, testing and
developing an MVC
application

2. Who I am
• Maxime Rouiller
• ASP.NET/IIS MVP
• 10 years of experience doing web development
• Freelancer
• Twitter: @MaximRouiller
• Blog: http://blog.decayingcode.com

3. The Plan
• My architecture and its different advantages
• Naming is subjective but must be clear
• How do I start my projects?
• What is the project structure that I use?
• What are my NuGet packages/libraries that I use?
• How do you test MVC Controllers?

4. 3-tier architecture
• Logic or physical architecture?
• Physical:
• Logical:
• MyProject.Web
• MyProject.Infrastructure
• MyProject.Business

5. Why separate your projects?
• Reusable components can actually be reused.
• Components are more easily testable
• Less likely to screw up (aka: circular references, using the wrong classes,
etc.)

6. Should I separateWebAPI and MVC?

7. Some rules…
• Just like an onion… you can only depend on
the layer bellow
• You can’t use a layer more than one level deep.
• Exception:When binding up a Dependency
Injection tool.

8. My Architecture: Onion/3 tier architecture
Advantages
• Easy to understand
• Easy to setup
• Reference rules can easily be enforced by a
source control
Disadvantages
• Depends on dependency injection
• Is not suited for very complex business logic
(see Domain Driven Design)

9. Architecture is a tool
• If what I suggested doesn’t fit your project, DO NOT USE IT.
• Architecture is a tool. If you only know one, you’ll use it on everything

10. My Libraries
• DataAccess: Entity Framework
• Why not <INSERTTECH HERE>?
• Inversion of Control container: Ninject
• JavaScript? Depends on the project. jQuery/AngularJS
• And more… way more smaller libraries
• UnitTesting: NUnit
• And Azure…

11. Your Library
• Use anything you feel comfortable!
• Please avoid NHibernate if possible
• Hard to master
• Steep learning curve
• Ensure that it uses NuGet.Why?

12. Demo
Creating some code to test!
Unit testing a controller
Project Structure with tests
Project Structure for scaling withWebAPI

13. Questions?
• Contact me onTwitter: @MaximRouiller
• Blog: http://blog.DecayingCode.com
• Add me to LinkedIn
• www.MaximeRouiller.com
• Or speak to me at the break!