Downgrade to .NET 4.8.0 #121
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
|
I am using windows server 2016 the .Net Framework 4.8.1 is not installable by this version of windows. .Net Framework 4.8.1 only adds support for Arm. Jellyfin.Windows.Tray.exe will not run after the upgrade due to this requirement. however you can still start the server manually. the Jellyfin server will still run. however the Tray app will not. to rectify this can you please set the .Net Framework requirement to 4.8 this will resolve the issue. |
nielsvanvelzen
requested changes
May 23, 2024
|
As explained in #122, I'm going to roll back to .NET 4.7.2 for the tray app. We don't currently build the tray app or installer for ARM, so we'll cross that bridge later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Compatibility of .NET 4.8.0 is way better than the one of 4.8.1: https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies#net-framework-48
Fixes #119