Target Framework Updates #389
Merged
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
* Reference Cysharp `ZString` v2.6.0 in `SmartFormat` project (net461 target use the netstandard2.0 assemblies) * Remove project `SmartFormat.Zstring` * Move internal static class ZStringBuilderExtensions to namespace SmartFormat.ZString * Rename ZStringBuilderExtensions to ZStringBuilderUtilities
* Flag `ZStringBuilder` and `ZStringWriter`with `[ExcludeFromCodeCoverage]` * Add AltCoverAttributeFilter="ExcludeFromCodeCoverage" in CI tests
* Directory.Build.props: Remove duplicate entries from Demo and Performance projects * Enable NRT for Demo and Performance projects * Remove folder SmartFormat.ZString from former projects SmartFormat.ZString * Remove obsolete entries from SmartFormat.sln * Remove reference to former SmartFormat.ZString.dll from SmartFormat.csproj
Fix nullability issues caused by net60 target framework
* Mark CTOR overload (System.Runtime.Serialization.SerializationInfo info, System.Runtime.Serialization.StreamingContext context) as obsolete (like it is in net8.0). * Update proprocessor directives and nuget packages * Change appveyor_build_worker_image to Ubuntu2204 * Add net8.0 as target framework * Update target framework net461 to net462
|
|
@karljj1 Somehow you got lost as a project maintainer. I have sent you a new invitation and hope you'll accept. Could you review this PR please? |
karljj1
approved these changes
May 15, 2024
|
Almost all of the 380 changed files are deletions coming form |
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.
.NET Framework 4.6.2
SmartFormat has transitioned to using
.NET Framework 4.6.2 (net462)as its target framework, replacing the now unsupported.NET Framework 4.6.1 (net461). The support fornet461ended in 2022, whilenet462will continue to receive support until January 2027.Switching to a different patch version of a target framework is generally not considered a breaking change. This is referred to as an in-place update by Microsoft. In the case of SmartFormat, we have not encountered any runtime issues with the existing API after this transition.
The same holds true for the new
netstandard2.0reference to ZString..NET 6.0 and .NET 8.0
SmartFormat has expanded its compatibility by adding
.NET 6.0 (net60)and.NET 8.0 (net80)as additional target frameworks. You can find details about their end of support here.All Target Frameworks
We have removed the
SmartFormat.ZStringassembly and replaced it with a reference to the ZString package. This change does not affect the API.