ASP.NET MVC: Resolve or Inject? Thats the Issue

Posted by: Simple Talk, on 23 Apr 2012 | View original | Bookmarked: 0 time(s)

Classes should have dependencies only on abstract, rather then concrete, clesses. To get around this, you can choose between Service Locator and Dependency Injection techniques. ASP.NET MVC uses 'Dependency Resolvers' which are Service Locators. When designing ASP.NET MVC applications it is open to you to decide whether to resolve or inject, so what are the pros and cons? Dino explains....

Category: ASP.NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 391 | Hits: 6

Similar Posts

  • How to use Ninject 2 with ASP.NET MVC more
  • ASP.NET MVC Controls and Good versus Evil more
  • Visual Studio Silent Crash with Designer more
  • Donut Caching in ASP.NET MVC more
  • Threading model issues when using VB 6 COM components in a .NET Web Service more
  • Getting Images to render properly in the ASP.NET Designer more
  • OpenForce07 Tuesday Afternoon: DNN Development Security more
  • Web Application Project Conversion Tips more
  • Forms Authentication Timeout more
  • .NET Framework FAQ : How do I dynamically resolve assemblies, types, and resources more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD