MicrosoftSo you deprecated System.Data.SqlClient without first updated dependent features such as typed datasets? When you add a typed dataset to a NET 8 project the System.Data.SqlClient namespace and libraries do not exist and after adding it a ton of warnings about being deprecated are displayed.
This is bad development practice to deprecate the objects before updating the dependent features such as datasets. Some of us want to use ADO and datasets for some projects.
MicrosoftNoted.
You might want to check out Entity Framework Core, though. Datasets are considered legacy and development efforts have been focused on EF Core for quite a long time now.
Datasets and related classes are legacy .NET Framework technologies from the early 2000s that enable applications to work with data in memory while the applications are disconnected from the database. The technologies are especially useful for applications that enable users to modify data and persist the changes back to the database. Although datasets have proven to be a very successful technology, we recommend that new .NET applications use Entity Framework Core. Entity Framework provides a more natural way to work with tabular data as object models, and it has a simpler programming interface.
