Pomelo.entityframeworkcore.mysql: Conflict with dependencies

[kristx300]

Pomelo.EntityFrameworkCore.MySql - require - MySqlConnector <1.0
HealthCheck.MySql - require - MySqlConnctor >1.0

Or write issue to HealthCheck repo?

[mguinness]

See Support for MySqlConnector >1.0 and Incompatible with MySqlConnector v. 1.x

[kristx300]

Checked.
Issue closed, but not solved.

[mguinness]

Also see Update MySqlConnector to 1.0 which is still open, but now redundant.

[kristx300]

In any case, I think we need to wait for the new release from HealthCheck.
Or PomeloFoundation will develop full support health check provider. That's sounds good.

[lauxjpn]

In any case, I think we need to wait for the new release from HealthCheck.

@kristx300 What is HealthCheck? Chan you provide us with a link?

There is an alpha prerelease of Pomelo available that is compatible with EF Core 5, which uses MySqlConnector >= 1.0.0.
See https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/issues/1088#issuecomment-707776730 for further details.

[kristx300]

One simple class and code.
MySqlHealthCheck.cs

[lauxjpn]

@kristx300 I see, so I am assuming you are using the MySqlHealthCheck.cs class, but also Pomelo 3.2.3 with EF Core 3.1.x.

So as mentioned above, you could just use EF Core 5 and the Pomelo 5.0 alpha prerelease.

If you want to keep using EF Core 3.1.x you could just use a HealthChecks release before https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/issues/612. Their MySql package version 3.1.1 should be the last one that supports MySqlConnector < 1.0.0.

You could also move the HealthChecks reference to a different project (can be in the same solution). Different projects can reference the same package in different versions.

[kristx300]

@lauxjpn I think, better way is to copy one class to ext lib in solution
And when HC fixes it, I can easily replace the code with lib

//I am waiting for the full release .Net 5 and base depends libs