The Missing Third Config Layer: Adding User Secrets to Blazor WebAssembly

🤔 The Problem with Blazor WebAssembly A while back, I wrote a Japanese article about how to manage API keys for error monitoring services like Raygun and Sentry in a Blazor WebAssembly app. https://qiita.com/jsakamoto/items/e72bbf0681994307d07c In that article, I touched on how to handle configuration values during development. Here is one passage I wrote: I think it would be a good idea to exclude appsettings.Development.json from version control using a .gitignore file, but I will skip the details in this article. If you were using a project other than Blazor WebAssembly, User Secrets would be a convenient and reasonable option. Unfortunately, Blazor WebAssembly does not support User Secrets, so using appsettings.Development.json seemed like the safest approach. Yes, Blazor WebAssembly does not support User Secrets . And this turns out to be more of a problem than it first appears. 🔍 The Three-Layer Configuration Problem In .NET apps, I think most developers want to manage configurat