.Net Framework - Microsoft.Data.SqlClient trusted certificate error though not using that driver

Question

This is a .NET Framework 4.8 console project, but there is no tag for that.

I am using Visual Studio 2022 - v17.10.1

When I try to add either an Entity Framework (v6.5.1) model from an existing SQL Server database, I get an error regarding a trusted certificate which most likely comes from Microsoft.Data.SqlClient - at least that's the where the exception comes from. I am using system.data.sqlclient though.

I am not using that driver at all for data access.

I tried adding TrustServerCertificate=true and Encrypt=False to the connection string, but that didn't make a difference because the program still connects to the database fine. I only have an issue when I try to add an Entity Framework Model.

Please note that the connection string I'm using to create the model is validating.

It almost looks like TrustServerCertificate=True is left off when creating the info in the app.config for the model.

Why would the connection string work, but creating the model not work?

Answer 1

This looks like it was caused by an incompatibility with EF Core Power Tools. As I also use Database First in EF Core, that is a necessary extension to provide functionality Microsoft removed.

Disabling the extension seems to have fixed the issue. I may contact the extension's authors about this.

Answer 2

Hi Reuben Cohen, 

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer. 

Ask:.Net Framework - Microsoft.Data.SqlClient trusted certificate error though not using that driver. 

Solution: The issue was caused by an incompatibility with EF Core Power Tools, which I use for Database First support in EF Core. Disabling the extension resolved the problem. 

If you have any other questions, please let me know. Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.