Remove .NET 4.5 targets and update to .NET 9 #80
Conversation
This file contains hidden or 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
- Remove net452 targets from all projects - Delete netfx.props (Mono support no longer needed) - Update test/example projects from net6.0 to net9.0 - Keep netstandard2.0 for library projects (TickSpec, TickSpec.Xunit) - Update GitHub Actions to .NET 9.0.x and actions v4 - Remove Linux framework workaround from Build.fs - Simplify Directory.Build.props (remove explicit FSharp.Core pinning) - Update package dependencies to latest versions: - NUnit 3.14.0, NUnit3TestAdapter 4.5.0 - Microsoft.NET.Test.Sdk 17.12.0 - Xunit 2.9.3, xunit.runner.visualstudio 3.0.1 - MSTest 3.7.0, Autofac 8.2.0, Expecto 10.2.1 - Microsoft.SourceLink.GitHub 8.0.0 - Fix Expecto API change (runTestsInAssemblyWithCLIArgs) - Fix NUnit CollectionAssert usage in Prelude.fs - Remove unnecessary System.Runtime references Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
bartelink
reviewed
Jan 23, 2026
| <Project Sdk="Microsoft.NET.Sdk"> | ||
| <PropertyGroup> | ||
| <TargetFramework>netstandard2.0</TargetFramework> | ||
| <TargetFramework>net9.0</TargetFramework> |
Member
There was a problem hiding this comment.
why not 6/8/10? (I tend to stick to 6 or 8 for libraries and would only pick 9 as a target if there was a high value API that was only available in 9, but even that doesnt make sense given 9 will be out of support soon and 10 is mainstream)
Collaborator
Author
There was a problem hiding this comment.
Thanks, I created this pull request mainly as a playground whether it is possible to solve the build issues on Mac and also enable the debugging breakpoints in newer .NET. Definitely good point to choose one of the LTS frameworks, have just chosen 9 as I had it locally installed to see whether I can get it working. Will do more tests with the debugging breakpoints and then will finalize this PR.
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.
Uh oh!
There was an error while loading. Please reload this page.