Bug #89856 Do not add docs directory in MySQL Connector/NET NuGet package
Submitted: 28 Feb 2018 17:26 Modified: 10 Aug 2022 18:42
Reporter: Jon Miller Email Updates:
Status: Not a Bug Impact on me:
Category:Connector / NET Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[28 Feb 2018 17:26] Jon Miller
When you add the MySql.Data NuGet package to a project in Visual Studio, it adds a docs directory with a bunch of xml files in it into every project that you are referencing the NuGet package from. I have no need for these files and have to manually remove them every time I upgrade the package.

Also, would it be possible to have it check App.config and only mess with it if the library isn't registered. And also, not include the version number? Personally, I like to register it like the following. That way it will work with any version and I don't have to mess with it. However, every time I upgrade the NuGet package, I have to go back in can clean everything up.

      <add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient" description=".Net Framework Data Provider for MySQL" type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data" />

At least stop adding the docs, it's just annoying and make me dread every having to do an update.

How to repeat:
Add the MySql.Data NuGet package to a C# project in Visual Studio. You will see that it has added a docs directory to your project containing useless XML files.

Suggested fix:
Do not add docs directory to projects. When updating App.config/Web.config, check if the libraries are already in there and don't mess with it if it is, other than changing the version number, or just outright removing the version number.
[1 Mar 2018 7:26] Chiranjeevi Battula
Hello Jon Miller,

Thank you for the bug report.
Verified this behavior on Visual Studio 2017 (C#.Net) and Connector/NET 6.10.6 version.

[1 Mar 2018 7:28] Chiranjeevi Battula

Attachment: Bug_89856.PNG (image/png, text), 17.44 KiB.

[16 Apr 2018 13:26] Jairo Assis
This is a really annoying bug. Do we have any idea of when the fix will be released? Thanks!
[10 Aug 2022 18:42] Daniel Valdez
This is no longer a bug. Please use our latest release, Connector/NET 8.0.30.