Resolving Services in Program.cs with .NET 7 ASP.NET Core

---

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---

Understanding the Challenge

As we move to a .NET 7 setup, this structure is streamlined, but while it simplifies app configuration, it may also feel less intuitive when attempting to resolve services directly.

A Solution for .NET 7

There are several ways to manage service resolution in .NET 7, but we'll focus on one particular method that I find effective. The process involves setting up a static class dedicated to all configuration tasks, including the seeding of your database with test data.

Step 1: Create a Static Class for Configuration

You will want to create a static class that contains extension methods for IServiceCollection and methods for adding test data. Here’s how you might structure it:

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

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

Key Takeaways

Simplified Configuration: The use of a static class and extension methods allows you to keep your configuration organized.

Manual Service Resolution: After building the application, you can access the services using app.Services—enabling you to resolve any required services, like your DbSeeder.

Flexibility: The new approach provides greater flexibility in how you structure your ASP.NET Core applications.

Conclusion

By following these steps and structures, you can easily implement service resolution in your ASP.NET Core applications while embracing the new features offered in .NET 7.