Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning ASP.NET Core 2.0

You're reading from   Learning ASP.NET Core 2.0 Build modern web apps with ASP.NET Core 2.0, MVC, and EF Core 2

Arrow left icon
Product type Paperback
Published in Dec 2017
Publisher Packt
ISBN-13 9781788476638
Length 516 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Michel Bruchet Michel Bruchet
Author Profile Icon Michel Bruchet
Michel Bruchet
Jason De Oliveira Jason De Oliveira
Author Profile Icon Jason De Oliveira
Jason De Oliveira
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. What is ASP.NET Core 2.0? 2. Setting Up the Environment FREE CHAPTER 3. Creating a Continuous Integration Pipeline in VSTS 4. Basic Concepts of ASP.NET Core 2.0 - Part 1 5. Basic Concepts of ASP.NET Core 2.0 - Part 2 6. Creating MVC Applications 7. Creating Web API Applications 8. Accessing Data using Entity Framework Core 2 9. Securing ASP.NET Core 2.0 Applications 10. Hosting and Deploying ASP.NET Core 2.0 Applications 11. Managing and Supervising ASP.NET Core 2.0 Applications

Using dependency injection for encouraging loose coupling within your applications


One of the biggest problems when developing applications is inter-component dependencies. These dependencies make it hard to maintain and evolve your components individually because modifications might badly impact other dependent components. But be assured, there are mechanisms that allow those dependencies to be broken up, one of them being dependency injection (DI).

Dependency injection allows components to work together, while providing loose coupling. A component only needs to know the contract implemented by another component to work with it. With a DI container, components are not directly instantiated nor are static references used for finding an instance of another component. Instead, it is the responsibility of the DI container to retrieve the correct instance during runtime.

When a component is designed with DI in mind, it is very evolutive by default and is not dependent on any other components or...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image