How To Keep SECRET Strings REALLY SECRET in ASP.NET Core?

wow good to know something new, So if the app in on prem and there's no CI/CD how do we switch between the user secrets based on environment ?

Environment variables and user secrets are not best practice for production. You should go for azure key vault.

Very useful video, thanks 😉👍 .
I got error "Could not find the global property 'UserSecretsId' in MSBuild project ...",
but helped me call "dotnet user-secrets init" before calling " dotnet user-secrets set ...", then all was ok 🙂 .

Thanks for clear explanation and good examples!

I got this problem when hitting the controller

"System.InvalidOperationException: The ConnectionString property has not been initialized."

Thanks for providing exactly the knowledge I needed. I'm gonna combine this with Gitlab environment variables when deploying the application.

Thank you Dan. On a side note. If you right mouse click on the project file, from the menu you can select "Manage User Secrets". Another way besides the command line. This is in VS 2022.

This is the information I need. Special thanks Dan. As always super clear explanation.

Normally one can use the AzureKeyVault to store the connection strings etc. when deploying your application. Is that correct?

Thank you for teaching me something new.

Excellent, as always

big thanks

thanks so much

Like always very good content, Thanks.