Currently, the ConnectionStrings.config is .gitignore’d in order to ensure that the database password is not exposed publicly. Since we’re hosting on Azure Web Apps, however, a more elegant approach is to use the new(er) secrets format—which reads from the secrets.json in the /Users directory in development, and from Azure’s Connection Strings configuration on the server.
Steps
[x] Configure the GoldSim connection strings with the Azure Web App
[x] Register a secrets.json file on Visual Studio
[x] Configure the GoldSim configuration strings in the secrete.json file
[x] Delete the ConnectionStrings.config
This is associated with the .NET Core 3.x Migration project—but, technically, it can be done at any time.
Currently, the
ConnectionStrings.configis.gitignore’d in order to ensure that the database password is not exposed publicly. Since we’re hosting on Azure Web Apps, however, a more elegant approach is to use the new(er) secrets format—which reads from thesecrets.jsonin the/Usersdirectory in development, and from Azure’s Connection Strings configuration on the server.Steps
secrets.jsonfile on Visual Studiosecrete.jsonfileConnectionStrings.configThis is associated with the .NET Core 3.x Migration project—but, technically, it can be done at any time.