You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2026/10/20 23:04:00 UTC

[jira] [Created] (THRIFT-6440) Let the .NET tool run where only .NET 9 or later is installed

Jens Geyer created THRIFT-6440:
----------------------------------

             Summary: Let the .NET tool run where only .NET 9 or later is installed
                 Key: THRIFT-6440
                 URL: https://issues.apache.org/jira/browse/THRIFT-6440
             Project: Thrift
          Issue Type: Bug
          Components: Build Process
            Reporter: Jens Geyer


{{Apache.Thrift.Compiler}} targets {{net8.0}}, and its project does not set {{RollForward}}. Such a tool runs only on a .NET 8 runtime. On a machine that has only .NET 9 or 10, {{dotnet tool install --global Apache.Thrift.Compiler}} succeeds, but {{thrift}} then refuses to start:

{noformat}
You must install or update .NET to run this application.

App: /t/thrift
Architecture: x64
Framework: 'Microsoft.NETCore.App', version '8.0.0' (x64)
.NET location: /usr/share/dotnet

The following frameworks were found:
  10.0.12 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]
{noformat}

This is the 0.25.0 package from nuget.org in the {{mcr.microsoft.com/dotnet/sdk:10.0}} image. The .NET host looks for the framework before any of the tool's code runs, the same way on Windows. Installed with {{--allow-roll-forward}}, or run with {{DOTNET_ROLL_FORWARD=Major}}, the launcher starts. The CI runners have .NET 8 next to newer versions, so the install-and-run test there does not notice.

Fix:
* {{<RollForward>Major</RollForward>}} in {{build/windows/dotnet-tool/Apache.Thrift.Compiler.csproj}}: the launcher then uses the next newer .NET when 8 is missing, and nothing changes where 8 is installed.
* {{test-dotnet-tool.ps1}} checks that the {{runtimeconfig.json}} in the package allows this.

The 0.25.0 package cannot be changed any more. For it, uninstalling the tool and installing it again with {{--allow-roll-forward}} works around the problem.

_Drafted with AI assistance (Claude Opus 5.5)._




--
This message was sent by Atlassian Jira
(v8.20.10#820010)