Log .NET runtime version #552

Merged
mattzink merged 2 commits from runtime-ver into master 2025-01-21 01:19:19 +00:00
mattzink commented 2025-01-21 00:51:07 +00:00 (Migrated from github.com)

I was looking into a crash, and found out it was an issue that was fixed in .NET 9.0.1. Since Ryujinx embeds the runtime into the executable, it not obvious which runtime a build uses. This logs the .NET runtime version immediately after the build version.

I was looking into a crash, and found out it was an issue that was fixed in .NET 9.0.1. Since Ryujinx embeds the runtime into the executable, it not obvious which runtime a build uses. This logs the .NET runtime version immediately after the build version.
GreemDev commented 2025-01-21 00:57:05 +00:00 (Migrated from github.com)

I don't feel this is necessary.
The contents of the repo already describe the version of .NET, and it doesn't change often.
You also can easily look at the contents of a repo as of a tag and look at the global.json file to see what version of .NET it uses, if you're using an older version and don't know what version of .NET it's on.

I don't feel this is necessary. The contents of the repo already describe the version of .NET, and it doesn't change often. You also can easily look at the contents of a repo as of a tag and look at the global.json file to see what version of .NET it uses, if you're using an older version and don't know what version of .NET it's on.
mattzink commented 2025-01-21 01:00:16 +00:00 (Migrated from github.com)

The global.json sets the minimum required SDK version. The issue I was tracking wasn't reproducible after I compiled because I had a newer SDK locally.

The global.json sets the _minimum_ required SDK version. The issue I was tracking wasn't reproducible after I compiled because I had a newer SDK locally.
mattzink commented 2025-01-21 01:17:24 +00:00 (Migrated from github.com)

I just double-checked and since there is a roll-forward policy set in the global.json and the build is using the setup-dotnet github action, then the latest 9.x.x version of the SDK will be selected/used automatically during each build. There is nothing therefore that tells someone which runtime version was embedded in a specific build.

I just double-checked and since there is a roll-forward policy set in the global.json and the build is using the setup-dotnet github action, then the latest 9.x.x version of the SDK will be selected/used automatically during each build. There is nothing therefore that tells someone which runtime version was embedded in a specific build.
Sign in to join this conversation.
No description provided.