.NETFX4.0 -> .NETFX48 target framework #15
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
Reason: Visual Studio 2022 dropped supported for .NET Framework 4.0 and odler. Furthermore, .NET Framework 4.0 isn't compatible with .NET Standard, which a lot of 3rd party libs available on Nuget require. For .NET Framework, this requires at least .NET Framework v4.6.1. The Runtime used by Windows when running the app is the latest .NET Framework v4 installed, which is usually NET Framework v4.8 anyway. Any later versions of .NET Framework v4 is binary compatible with .NET Framework 4.0 apps. As for app requirements, .NET Framework 4.8 is a part of Windows since the Windows 10 May 2019 update. Finally, the binaries produced by the compiler when targeting the .NETFX4.8 should be identical as when target .NETFX4.0 (same MSIL) Signed-off-by: Maximilien Noal <[email protected]>
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.
Reason: Visual Studio 2022 dropped support for .NET Framework 4.0 and older.
Furthermore, .NET Framework 4.0 isn't compatible with .NET Standard, which a lot of 3rd party libs available on Nuget require. For .NET Framework, this requires at least .NET Framework v4.6.1.
The Runtime used by Windows when running the app is the current .NET Framework v4, which is usually NET Framework v4.8 anyway. Any later versions of .NET Framework v4 is used to run .NET Framework 4.0 apps.
As for app requirements, .NET Framework 4.8 is shipped with Windows since the Windows 10 May 2019 update.
Finally, the binaries produced by the compiler when targeting .NETFX4.8 should be identical as when target .NETFX4.0 (same MSIL)
Process: All the changes where generated by Visual Studio, which has asked for and done the .NETFX 4.8 migration itself.
Other details: The .NET Framework 4.0 Client Profile (a lighter runtime, essentially for thick client apps only) was dropped in later releases on the .NET Framework, this is why any reference to it is removed.
Also, the 'Prefer32Bit' was presumably removed because nowadays the x86_64 platform is everywhere.