In reply to @mattsturg:matrix.org

Hi, I just got started bumping nexusmods-app to v0.7.0 (wip branch).

Upstream have updated dotnet 8 -> 9, however it looks like some components still expect dotnet 8? I get this error when attempting to build the updated derivation if I bump dotnet to sdk 9:

  NexusMods.Networking.Downloaders -> /build/source/src/Networking/NexusMods.Networking.Downloaders/bin/Release/net9.0/NexusMods.Networking.Downloaders.dll

  You must install or update .NET to run this application.

  App: /nix/store/gnviywnlb7wqxz4dxcz9k55fbqpch51w-StrawberryShake.Server-14.1.0/share/nuget/packages/strawberryshake.server/14.1.0/tools/net8/dotnet-graphql.dll
  Architecture: x64
  Framework: 'Microsoft.NETCore.App', version '8.0.0' (x64)
  .NET location: /nix/store/a03c70i7x6rjdr6vikczsp5ck3v6rixh-dotnet-sdk-9.0.100/share/dotnet/

  The following frameworks were found:
    9.0.0 at [/nix/store/a03c70i7x6rjdr6vikczsp5ck3v6rixh-dotnet-sdk-9.0.100/share/dotnet/shared/Microsoft.NETCore.App]

  Learn more:
  https://aka.ms/dotnet/app-launch-failed

  To install missing framework, download:
  https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=8.0.0&arch=x64&rid=linux-x64&os=linux

/build/nuget.5WFLlF/fallback/strawberryshake.server/14.1.0/build/StrawberryShake.Server.targets(73,5): error MSB3073: The command "dotnet "/build/nuget.5WFLlF/fallback/strawberryshake.server/14.1.0/build/../tools/net8/dotnet-graphql.dll" generate "/>

Am I supposed to make multiple dotnet versions available during the build? If so how? If not, any other ideas?

Apparently buildDotnetModule is trying to run libs? cc Corngood

I guess this usually a non-issue and fails gracefully with a warning, but in this case the library we're trying to run is failing hard with an error because it expects .net8?

There are a lot of places where combinePackages is currently being used that really only need the nuget packages from another SDK/runtime. I'm actually trying to clean that up right now.

This looks like something else. Like it actually needs the net8 runtime, which is odd.

You can also set this to the result of dotnetSdkPackages.combinePackages, if the project uses multiple SDKs to build.

Ah, I should have RTFM before asking here! Thanks for the pointer

2024-12-01 02:09:50,925 [   3385] SEVERE - #c.i.o.p.i.ProjectManagerImpl - project loading failed
java.lang.IllegalStateException: No protocolHost for the application
	at com.jetbrains.rider.protocol.ApplicationProtocolKt.K(ApplicationProtocol.kt:73)
	at com.jetbrains.rider.protocol.ApplicationProtocolKt.getProtocolManager(ApplicationProtocol.kt:22)
	at com.jetbrains.rider.projectView.SolutionInitializer.initSolution(SolutionInitializer.kt:37)
	at com.jetbrains.rider.projectView.SolutionManager.K(SolutionManager.kt:465)
[...]

https://github.com/NixOS/nixpkgs/pull/360923

Here's a PR that adds dotnet-sdk_9, etc. I intend to backport it to 24.11.

I'm curious what people think about sdk/runtime naming. We currently have minor version SDKs that aren't accessible at the top level, e.g. dotnetCorePackages.sdk_8_0_1xx.

Should we add dotnet-sdk_8_0_1xx?

In reply to @corngood:corngood.com

https://github.com/NixOS/nixpkgs/pull/360923

Here's a PR that adds dotnet-sdk_9, etc. I intend to backport it to 24.11.

I'm curious what people think about sdk/runtime naming. We currently have minor version SDKs that aren't accessible at the top level, e.g. dotnetCorePackages.sdk_8_0_1xx.

Should we add dotnet-sdk_8_0_1xx?