A last week I wrote about fixing some problems between Git and Team Foundation Server 2018 when TFS is configured to use a self-signed SSL certificate for HTTPS.  Well, after I got that part working, I found a new problem while trying to configure a TFS build agent that would talk to my self-signed SSL…

If you’ve gone digging around in EF Core and ASP.NET Core, you’ve probably seen ConfigurationBuilder code that looks like this: var builder = new ConfigurationBuilder()     .SetBasePath(basePath)     .AddJsonFile(“appsettings.json”)     .AddJsonFile($”appsettings.{environmentName}.json”, true)     .AddEnvironmentVariables(); var config = builder.Build(); var connstr = config.GetConnectionString(“default”); When you see generated code like this a couple zillion times, it’s easy to kind of forget to ask yourself what it means.  It works fine so nevermind…

Earlier this year, I blogged about how to do EF Core migrations without hard-coding your connection string.  The short answer was to use IDbContextFactory.  Well, that was Entity Framework Core 1.0 and now we’re on Entity Framework Core 2.0 and that IDbContextFactory interface went away. So how to do you do EF Core 2.0 migrations…