When adding DataSet in ASP.NET Framework 4.7.2 project in Visual Studio 2022 it automatically adds NuGet Package for Microsoft.Data.SQLClient after updating the version from 17.4.3

Kalsofte 5

Whenever we add a new DataSet and Table Adapter in ASP.NET Web Site (Framework 4.7.2) in Visual Studio 2022, it automatically adds NuGet Package for Microsoft.Data.SQLClient. It was not happening in the version 17.4.3 and previous versions of VS2022. After updating to the latest version of VS 2022 probably from 17.5.x the issue started. We want to stick to System.Data.SQLClient and do not want this automatic addition of Microsoft.Data.SQLClient which results in inclusion of few hundreds of files under packages. We are forced to use VS2019 for just adding datasets to our ASP.NET Web Site.

Lan Huang-MSFT 25,471 Reputation points Microsoft Vendor

2023-06-08T06:52:38.74+00:00

Hi @Kalsofte,

Sorry, after I updated Visual Studio, I didn't find that NuGet Package will be added automatically.

You can check package settings via Tools > Options > NuGet Package Manager > General.

The following link is Restore packages in Visual Studio, you can set the opposite operation to see if it can be prevented.

If it still doesn't work, I think you can manually uninstall Microsoft.Data.SQLClient, and then download System.Data.SQLClient.

Install and manage packages in Visual Studio using the NuGet Package Manager
Lan Huang-MSFT 25,471 Reputation points Microsoft Vendor

2023-06-13T08:26:34.5033333+00:00

Deleted
Kalsofte 5 Reputation points

2023-06-15T11:24:03.4533333+00:00

Sorry for the delay in communicating the status of the issue. The issue persists whenever I add a new DataSet and add TableAdapter with existing stored procedure for Select operation. The WEB.CONFIG of my ASP.NET WebSite Project have the connectionstring with the provider System.Data.SQLClient. It is really painful to remove the auto-added packages and the files in the Bin folder flooded by Microsoft.Data.SQLClient provider which is not required for my .NET Framework 4.7.2 WebSite. If I remove the connectionstring in the WEB.CONFIG and choose new connection when adding the new DataSet, and choose the provider "Öther" and select .NET Framework provider for SQL Server and save the connectionstring with the same name as before, everything will work fine without any issues. The wizard will not add Microsoft.Data.SQLClient but it will specify the System.Data.SQLClient in the WEB.CONFIG and in the .XSD file too. This cannot be a workaround to stick to the System.Data.SQLClient and need better solution from Microsoft. Why is it forces to use Microsoft.Data.SQLClient for a .NET Framework project?
Kalsofte 5 Reputation points

2023-06-15T11:26:56.9766667+00:00
Lan Huang-MSFT 25,471 Reputation points Microsoft Vendor

2023-06-16T06:44:39.6733333+00:00

Hi @Kalsofte,

I reproduced your problem, unfortunately the Microsoft documentation doesn't provide instructions, now Visual Studio 2022 seems to use Microsoft.Data.SqlClient by default when you add a Table Adapter or DataSet. Microsoft has decided to discontinue the development of System.Data.SqlClient to focus on Microsoft.Data.SqlClient instead.

I think you can go to the visual studio forum for help, which can help you solve the problem better.

https://developercommunity.visualstudio.com/home