Join us this Friday for AI in Action at the Virtual Happy Hour! This free virtual event is open to all—enroll now on Academy and don’t miss out.
Join us this Friday for AI in Action at the Virtual Happy Hour! This free virtual event is open to all—enroll now on Academy and don’t miss out.
Hi, We.config contains the connection string details. You can do transformations, depending on enviornment and CI strategy.
/K
Hello @Daman,
I'm right on with @K Khan. I use the "main" web.config to point to the database I'm working on locally whether it's a shared DB or hosted on my local. Then, I use web.config transformations to make environment-specific configuration changes like connection strings, azure connections, Episerver Find Service URL, and pointing to Azure BLOB/Events. Just make sure your publishing profile points to the correct build configuration.
Hope this helps!
-RJ
Wanted to check how others are developing locally with the DB and on the cloud. Even though I have ignored the DB file to move on source control everytime I publish from TFS, the deployment fails and is always looking for a DB file? wanted to know how others are doing development with DB on LOCAL and on Azure?