Скачать или смотреть Integrating Microsoft.Extensions.DependencyInjection in ASP.NET .NET Framework 4.6.1 Projects

Learn how to effectively implement `Microsoft.Extensions.DependencyInjection` in your ASP.NET Framework 4.6.1 project to enable dependency injection.
---
This video is based on the question https://stackoverflow.com/q/68861721/ asked by the user 'Zorev Gnoz' ( https://stackoverflow.com/u/5105438/ ) and on the answer https://stackoverflow.com/a/68906335/ provided by the user 'Steven' ( https://stackoverflow.com/u/264697/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Integrating Microsoft.Extensions.DependencyInjection in ASP.NET 4.6.1 project

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Integrating Microsoft.Extensions.DependencyInjection in ASP.NET Framework 4.6.1 Projects

In the world of software development, Dependency Injection (DI) has become a fundamental concept for creating scalable and maintainable applications. While many developers are familiar with implementing DI in .NET Core projects, the challenge arises when trying to integrate Microsoft.Extensions.DependencyInjection into older projects that utilize .NET Framework 4.6.1. In this guide, we will clarify how to tackle this problem efficiently, enabling you to harness the power of DI in your legacy ASP.NET web applications.

Understanding the Problem

When moving from .NET Core to .NET Framework, you may notice differences in the structure and lifecycle of an application. In .NET Core, the Startup.cs class defines the application's entry point with a clear organization for service configuration. Conversely, ASP.NET applications operating under the .NET Framework typically use Global.asax.cs to initiate the application.

Let’s examine the scenario in which you want to register a service, IMemberServices, with its implementation, MemberService, in an ASP.NET Web API project that targets .NET Framework 4.6.1.

Step-by-Step Solution

1. Create a Custom Controller Activator

To use Dependency Injection in an ASP.NET Web API application, you'll need to implement a custom controller activator by adhering to the System.Web.Http.Dispatcher.IHttpControllerActivator interface. This provides a clear mechanism to create controller instances that leverage the DI container.

Here’s a breakdown of the necessary code:

[[See Video to Reveal this Text or Code Snippet]]

2. Register Services in Application_Start

Next, you need to configure your application to use this custom activator in the Application_Start method found in Global.asax.cs. Below is an example of how to do this. You’ll also need to register your controllers and other services through ServiceCollection before establishing the ServiceProvider.

[[See Video to Reveal this Text or Code Snippet]]

3. Why Use IHttpControllerActivator

Using IHttpControllerActivator is generally simpler and more structured than creating a custom IDependencyResolver. This approach grants you a centralized point for beginning a new IServiceScope, necessary for resolving controllers effectively without causing memory leaks or threading issues.

Conclusion

By following the steps outlined in this guide, you can successfully integrate Microsoft.Extensions.DependencyInjection into your ASP.NET Framework 4.6.1 projects. This will enable you to implement the practices of modern dependency injection, leading to better application architecture, improved testing capabilities, and enhanced code maintainability. Embrace the change, and enhance your legacy applications with the benefits of DI!

If you have any further questions or need assistance with implementation, feel free to reach out in comments below!