Replies: 1 comment 4 replies
-
|
I see that 2.1.x nugets ship assembly with 2.0.0 version. Is it expected change in v2 branch? v0/v1 releases had assembly version matching nuget version. |
Beta Was this translation helpful? Give feedback.
-
|
The version info on the DLL in the nupkg looks correct to me:
Are you talking about the strong name? |
Beta Was this translation helpful? Give feedback.
-
If yes, then note that this is a recommended best practice:
https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/versioning#assembly-version |
Beta Was this translation helpful? Give feedback.
-
|
Yep, version in strong name (one, returned by |
Beta Was this translation helpful? Give feedback.
-
|
OK, yes it is expected behaviour.
AFAIK they had a major-number-only strong name version, too. I don't actually know exactly where it comes from. The build chain generates |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Pipelining = False;in the connection string.MySqlCommand.Attributescollection to send them to the server when the command is executed.MySqlDecimalsupport: Implement MySqlDecimal #1070.MySqlDataReader.GetXexceptions forNULLvalues: Unhelpful exception message when reading NULL value #1092.MySqlConnector.Logging.Microsoft.Extensions.Logging
MySqlConnector.by default: MySqlConnector.Logging.Microsoft.Extensions.Logging is not prefixing the category name like other loggers #1080.MicrosoftExtensionsLoggingLoggerProvider(loggingFactory, omitMySqlConnectorPrefix: true)..UseMySqlConnectorLogging()extension method to add logging easily.This discussion was created from the release 2.1.0.
Beta Was this translation helpful? Give feedback.
All reactions