-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a NuGet package README to distinguish and inform consumers on each SQLClient package #2764
Comments
Thank you for raising the issue that consumers of Microsoft.Data.SqlClient package might not be aware of the differences of System/Microsoft packages. The porting-cheat-sheet from System.Data.SqlClient to Microsoft.Data.SqlClient should help to introduce the difference between the two packages. This cheat-sheet is already referenced in the README. We will discuss if the nuget package README should be updated with the same information. |
@JonDouglas I've been considering this. Thank you for bringing it up. I will test it to see how it works. I’m fairly certain that snupkg files (pdbs) do not include READMEs, but at least the nupkg package will have that feature. |
@JonDouglas to add more we can only do this on Microsoft.Data.SqlClient |
You should be able to use the old README experience for the older package and use the new one for packages that are actively built! |
I was reading through this tweet in which consumers weren't aware of the differences of System/Microsoft packages:
https://x.com/terrajobst/status/1821683056115376129
#1963
We recently have added README functionality to NuGet.org and soon you will be able to view these READMEs in your favorite IDE/editor experience as well like Visual Studio & VS Code.
It may be worth adding package READMEs to both packages for their next update to describe these packages further and what scenarios one should use them with. Here's a blog with more information on this:
https://devblogs.microsoft.com/nuget/write-a-high-quality-readme-for-nuget-packages/
The text was updated successfully, but these errors were encountered: