10.21.0 - Detected package version outside of dependency constraint

[rcollette]

When I perform a build, I am getting the following warning

[NU1608] Warning As Error: Detected package version outside of dependency constraint: Pomelo.EntityFrameworkCore.MySql 9.0.0 requires Microsoft.EntityFrameworkCore.Relational (>= 9.0.0 && <= 9.0.999) but version Microsoft.EntityFrameworkCore.Relational 10.0.0 was resolved.

Can these driver packages be made optional by setting the PrivateAssets attribute to 'all' since we don't need them all?

ex.

<ItemGroup>
  <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="8.0.0" PrivateAssets="all" />
  <PackageReference Include="Npgsql.EntityFrameworkCore.PostgreSQL" Version="8.0.0" PrivateAssets="all" />
</Item
``

[videokojot]

per the PomeloFoundation/Pomelo.EntityFrameworkCore.MySql#2017 (comment)
the pomelo 9 works well with the ef core 10.

Not sure iiuc the solution with the privateassets=all, how this should help?

[rcollette]

I'm not stating whether it does or does not work with EF Core 10, I'm merely stating that in this scenario, a warning is generated, that may be avoided by not forcing consumers of this package to have a transient dependency on Pomelo 9.

privateassets=all makes it so that packages/projects that depend on this package, will not include the dependency as a transitive dependency.

even better, to make the EFCore.BulkExtensions.MIT package smaller use IncludeAssets="compile" PrivateAssets="all" together, in which case these dependencies will not be bundled into the assembly.

Consumers of this package will already have references to the necessary database providers, just to setup connections and EF. There is no need for this package to force a transient dependency on unnecessary providers.

[videokojot]

I actually think is it is other way round and I do not want the privateassets=all at all.

I want to force some specific version, since the db provider can change I do not want the consumer have to guess which version of the to use..
But having explicit transitive (not transient) dependency I can assure the consumer that BulkExtension package actually works with such version (by having green tests).

I also think it's actually desired to have the warning generated (which would the privateassets=all hide, since there is not yet Pomelo for v10), so it's acknowledgment/reminder that we are using the v9 Pomelo for the v10 version (which is supported).