Loading Customer-Specific Configuration in ASP.NET Core (Blazor) at Startup

Discover how to manage customer-specific configuration for ASP.NET Core (Blazor) applications across multiple IIS sites using application pool identification.
---
This video is based on the question https://stackoverflow.com/q/64754465/ asked by the user 'Sc0tTy' ( https://stackoverflow.com/u/2404961/ ) and on the answer https://stackoverflow.com/a/64925758/ provided by the user 'Sc0tTy' ( https://stackoverflow.com/u/2404961/ ) 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: ASP.NET Core (Blazor) Loading customer specific configuration on startup by using Url or Virtual Path

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.
---
Loading Customer-Specific Configuration in ASP.NET Core (Blazor) at Startup

Managing configuration settings that differ based on the customer is a common challenge for developers, especially when running multiple instances of the same application under different URLs. This guide addresses how to efficiently load customer-specific configurations in an ASP.NET Core (Blazor) application at startup. This solution is vital for scenarios where the same application runs in different sites within Internet Information Services (IIS).

The Problem

When working with a server-side Blazor application in .NET Core 3.1 that hosts numerous sites for various customers, each instance may require different configuration settings. In traditional ASP.NET applications, developers could easily grab the virtual path or subdomain during the startup process to load the respective configurations.

However, with the evolution to .NET Core, particularly ASP.NET Core, there is no direct way to access these details in the Startup.cs without some clever workarounds. Here’s a closer look at the setup we are dealing with:

Multiple IIS Sites: Each site is dedicated to a different customer.

Configuration Storage: Each customer's configuration is stored in a specific config file, but retrieving this data directly from a database is not an option due to the sensitivity of connection details.

The Solution: Utilizing Application Pool ID

The good news is there's a practical way to tackle this problem: leveraging the Application Pool ID from the environment variables at startup. Below, we will explore how to implement this solution effectively.

Step-by-Step Implementation

Access the Application Pool ID: The first step is to grab the Application Pool ID from the environment variables during the ConfigureServices method.

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

Parse the Application Pool ID: Define a function SomeMagicToParseAppPool that takes the Application Pool ID and determines the corresponding section name that matches your customer configuration.

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

Load the Configuration Section: Use the section name to retrieve the configuration settings specific to that instance.

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

Considerations and Downsides

While this method is effective, it is noteworthy that each application requires its own Application Pool. This requirement is mainly due to how .NET Core applications handle unmanaged code and run within their individual application pools. This approach ensures that configurations are separated correctly, providing a layer of security and specificity.

Conclusion

Integrating customer-specific configurations in ASP.NET Core (Blazor) applications is not just a matter of convenience but also essential for ensuring smooth operational processes across multiple clients. By utilizing the Application Pool ID, developers can seamlessly load the configurations tailored to each customer, enabling smooth functionality across different instances.

With this approach, you can maintain your application’s flexibility while fulfilling the unique requirements of each user. If you're managing multiple sites with distinct configurations, this solution will undoubtedly aid in presenting a robust architecture for your Blazor applications.