Move appSettings.json values to User Secrets

Learn how to move certain values from appSettings.json into userSecrets. This video covers setup of user secrets, as well as explanation of how to get the values out after, where the files would be stored on your competer, etc. This also covers why you do not want to have passwords or other sensitive values in source control and what to do about existing source files with secrets after moving them to a better location. Datavids presents a easy follow along video on credentials management, and wishes you great success with your dotnet project!

[@Nebb_]

Thank you so much for making this, it took me way too long to find a up to date video on this.

[@mustseeiran6255]

Hi, what about hosting in IIS? Is secret applicable?

[@xardasu3646]

If another user create a new dotnet new user-secrets in his local, will it cause a conflict in the .sln file when commiting because different computer will generate different UserId ?

[@maximilianoviand7683]

And what happens if a person downloads the repository and lets say that the project needs both username and password in order to work. Wouldn't that be a problem since there wont be any secrets.json in the other person's computer. Great vid btw

[@maximilianoviand7683]

The same could be apply for an API key, encryption key, etc.

[@PIMARINE]

I would never share Your secrets. .. Especially the ones in Thailand.🤣🤣🤣

[@DataVids]

Lol you are too much man. I bet people come to this channel to here your funny comments not to watch the show.