Summary
EF Core Design's dependency on Microsoft.CodeAnalysis.Common (= 4.8.0) causes conflicts with other libraries, which use the newest version (4.11.0). This results in warnings about dependency mismatches:
Detected package version outside of dependency constraint: Microsoft.CodeAnalysis.Workspaces.MSBuild 4.8.0 requires Microsoft.CodeAnalysis.Common (= 4.8.0) but version Microsoft.CodeAnalysis.Common 4.11.0 was resolved.
While the app compiles and runs without errors, this could lead to runtime issues in scenarios where EF Core Design or the conflicting library requires specific features or behaviors from their respective versions of Microsoft.CodeAnalysis.Common.
Proposed Solution
Consider updating EF Core Design's dependency constraints to >= 4.8.0 instead of = 4.8.0, or update to a newer version compatible with the latest libraries.
Steps to Reproduce
Create a project with EF Core Design v9.0 and Wolverine 3.3 (or any other library with a dependency on Microsoft.CodeAnalysis.Common v4.11).
Observe the dependency conflict warning during restore or build.
Impact
This restrictive dependency constraint creates avoidable warnings and potential runtime issues in projects integrating multiple libraries.
Summary EF Core Design's dependency on
Microsoft.CodeAnalysis.Common (= 4.8.0)
causes conflicts with other libraries, which use the newest version (4.11.0). This results in warnings about dependency mismatches:Detected package version outside of dependency constraint: Microsoft.CodeAnalysis.Workspaces.MSBuild 4.8.0 requires Microsoft.CodeAnalysis.Common (= 4.8.0) but version Microsoft.CodeAnalysis.Common 4.11.0 was resolved.
While the app compiles and runs without errors, this could lead to runtime issues in scenarios where EF Core Design or the conflicting library requires specific features or behaviors from their respective versions of
Microsoft.CodeAnalysis.Common
.Proposed Solution Consider updating EF Core Design's dependency constraints to
>= 4.8.0
instead of= 4.8.0
, or update to a newer version compatible with the latest libraries.Steps to Reproduce
Impact This restrictive dependency constraint creates avoidable warnings and potential runtime issues in projects integrating multiple libraries.
Thank you for considering this improvement!