Dependency conflict (downgrade)

[RobertoPeters]

I have updated all my packages to the most recent version (dotnet 10), but then I run into package downgrades:
Looks like the JaspeFx.RuntimeCompiler (4.2.0) requires the Microsoft.CodeAnalysis (4.14.0) instead of the 5.x
This prevents me from upgrading to the most recent WolferineFX package version (without warnings at least)

[jeremydmiller]

@RobertoPeters Just curious, what do you have that requires the CodeAnalysis 5.*?

[jeremydmiller]

I'm just bumping it in JasperFx, then bringing it through.

[RobertoPeters]

@jeremydmiller , thank you for the change. And regarding your question about why 5.* for CodeAnalysis?
I am using it in my project The Ultimate Automation Tool (https://github.com/RobertoPeters/TheUltimateAutomationTool)
It is an application to create automations and one of its strengths is that the user can select a script language (like JavaScript or Python). One of these languages is C#. And I would like to have the most recent version available for the user. Is it really needed? Maybe not, But I like to stay on top of things and therefor, I always update to the most recent package version.

[maximerety]

@jeremydmiller This issue does not seem to be fully resolved.

I've created an empty project with this .csproj file:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="WolverineFx.EntityFrameworkCore" Version="5.9.0" />
  </ItemGroup>
</Project>

And running dotnet restore triggers the following warning:

/Users/maximerety/Work/metalgear/liquid-server/src/Empty/Empty.csproj : warning NU1608: Detected package version outside of dependency constraint: Microsoft.CodeAnalysis.Workspaces.MSBuild 4.14.0 requires Microsoft.CodeAnalysis.Workspaces.Common (= 4.14.0) but version Microsoft.CodeAnalysis.Workspaces.Common 5.0.0 was resolved.

It looks like some other package than JaspeFx.RuntimeCompiler is pulling the old version of Microsoft.CodeAnalysis.Workspaces.MSBuild.

[jeremydmiller]

@maximerety Actually, sorry, I think I need a slight delay. In your codebase where you've tried to upgrade Wolverine, can you look at the project.assets.json file and let's see where the offending Nuget deps are coming from? Just a quick Ctrl-F on "CodeAnalysis" will help. Could be something from outside of the Critter Stack, which might still take an adjustment of our Nuget dep ranges, but still.

Answer in Slack if you would please.

Nevermind, let me try your blank project in a bit.

[corentinbst]

This does not appear to be corrected unless something is wrong on my end. I installed WolverineFx in my application project and EntityFrameworkCore.Design in both my API and authorization server. They depend from Infrastructure which in turn depend on Application.

Rider tells me Application uses Microsoft.CodeAnalysis.* 4.14.0 (referenced implicitly by WolverineFx) but my other projects use 5.0.0 (referenced implicitly by EntityFrameworkCore.Design).

This prevents me from generating my ef core migrations.

[jeremydmiller]

@corentinbst EF Core is just about the worst source of diamond dependency conflicts, with the CodeAnalysis being right up there. Dunno without seeing you project.

[corentinbst]

@jeremydmiller Thank you for the quick response. I have attached a few screenshots of my NuGet tool in Rider.

On the first one you can see Application references CodeAnalysis.Common (but this is true for other CodeAnalysis.XXX packages, 7 in total IIRC) 4.14.0 due to WolverineFx

And on this one you can see that 5.0.0 is referenced by EntityFrameworkCore.Design (10.0.X)

It is weird, because the dependency comes from JasperFx.RuntimeCompilation which allows for CodeAnalysis 4.14.0 .. 6.0.0, when looking at the dependencies. I have no particular NuGet configuration that could mess it up