How to Move the ConfigureServices Method to Another Class in ASP.NET Core

Learn how to organize your ASP.NET Core project by moving the `ConfigureServices` method to a separate class file for better structure and maintainability.
---

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: Write ConfigureServices Method In Another Class File

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Introduction: The Problem of Organizing ConfigureServices in ASP.NET Core

The Initial Setup

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

As you can see, the ConfigureServices method includes several AddTransient service registrations. While this approach is straightforward, there is a cleaner, more organized way to handle it.

Creating a Separate Class for Service Registrations

To clean up your code structure, we will create a new class where the service registrations will reside. This will allow you to better manage your application’s dependencies.

Step 1: Create the New Class

Let's assume we name our new class ServiceRegistration. Inside it, we can move the registrations from the Startup class:

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

Step 2: Implementing the Changes

Creating an Abstract Base Class:

By making StartUpBase an abstract class with a virtual method ConfigureServices, we can define a place for shared service registrations.

Overriding in the Concrete Class:

The StartUp class inherits from StartUpBase. Here, we can call the base method to maintain the service registrations while adding any additional services we need.

Alternative Approach

If you prefer a non-inheritance based solution, you can use a static method for handling service registrations:

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

By creating an extension method for IServiceCollection, we can maintain clear separation and organization of service registrations.

Conclusion

If you have further questions on this topic or need assistance with ASP.NET Core, feel free to reach out!