A while ago, I had a situation where a DbContext was misbehaving after deployed to an Azure App Service, and I needed to check the connection string it’s using directly in the code.
However, finding the right method actually took me googling, as there were plenty of examples for Entity Framework for .NET Framework, but next no nothing for Entity Framework Core. Let’s fix that.
Long story short, here’s how:
ApplicationDbContext db; // injected in the constructor of the controller db.Database.GetDbConnection().ConnectionString // fetch the DbConnection object and grab its Connection String
This applies to .NET Core + EF Core (at least starting form around version 3.0).
Oh – a quick word of advice: The connection string will contain your password. Don’t log it anywhere as is. If you plan to push it to Application Insights or something, remove the password from the string before doing that.
Developer / Architect / Consultant at Koskila / Valo Solutions Ltd. / Norppandalotti Software Co / Alter - Experience Ideas Ltd.
Antti Koskela is a proud digital native nomadic millennial full stack developer (is that enough funny buzzwords? That's definitely enough funny buzzwords!), who works as a Solutions Architect for Valo Intranet, the product that will make you fall in love with your intranet.
He's been a developer from 2004 (starting with PHP and Java), and he's been bending and twisting SharePoint into different shapes since MOSS. Nowadays he's not only working on SharePoint, but also on .NET projects, Azure, Office 365 and a lot of other stuff. He's also Microsoft MVP for Office Development.
This is his personal professional (e.g. professional, but definitely personal) blog.
He's been a developer from 2004 (starting with PHP and Java), and he's been bending and twisting SharePoint into different shapes since MOSS. Nowadays he's not only working on SharePoint, but also on .NET projects, Azure, Office 365 and a lot of other stuff. He's also Microsoft MVP for Office Development.
This is his personal professional (e.g. professional, but definitely personal) blog.
Latest posts by Antti K. Koskela (see all)
