Assembly version remains unchanged across SDK releases, causing upgrade issues

[tsaiggo]

trafficstars

Describe the issue I noticed that the assembly version has remained fixed at 2.0.0.0 across different SDK releases, including v2.2.7 and v2.4.0.

This can cause problems during system upgrades, as the DLL may not be replaced if both the file name and assembly version remain unchanged.

Expected behavior Ideally, the assembly version should be updated in line with SDK version upgrades to ensure that new versions are properly deployed and recognized.

Questions

Is there a specific reason why the assembly version is intentionally kept unchanged?

Would it be possible or advisable to increment the assembly version along with SDK releases to avoid upgrade inconsistencies?

Thank you for your clarification and support!

[bgrainger]

MySqlConnector follows the best practices for assembly versioning from https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/versioning#assembly-version:

✔️ CONSIDER only including a major version in the AssemblyVersion.

In fact, MySqlConnector doesn't even set AssemblyVersionAttribute but lets the project system generate it using the (recommended) defaults.

You wrote:

This can cause problems during system upgrades, as the DLL may not be replaced if both the file name and assembly version remain unchanged.

Are you talking about installing MySqlConnector in the GAC?

I'm not sure why you would want to do that, but would advise against doing so. Instead, copy all dependent packages into the program's "bin" folder.