Skip to content

feat: re-support net46 and netstandard2.0 targets#429

Merged
mysticmind merged 2 commits into
5.xfrom
feature/downlevel-netstandard2.0-net46
Jul 6, 2026
Merged

feat: re-support net46 and netstandard2.0 targets#429
mysticmind merged 2 commits into
5.xfrom
feature/downlevel-netstandard2.0-net46

Conversation

@mysticmind

Copy link
Copy Markdown
Owner

Add net46 and netstandard2.0 back to the target frameworks, guarding net6+/net7+ APIs (GeneratedRegex, Regex.EnumerateMatches, span line splitting, range/index operators) behind conditional compilation and BCL polyfills (ReplaceLineEndings, DistinctBy, GetValueOrDefault, char-based Contains/StartsWith/EndsWith).

Test project drops Verify in favour of plain assertions and checked-in snapshots so the suite runs on net48/net6.0, with downlevel-compatible test tooling. CI builds every TFM on Linux and runs net48 on Windows.

Add net46 and netstandard2.0 back to the target frameworks, guarding
net6+/net7+ APIs (GeneratedRegex, Regex.EnumerateMatches, span line
splitting, range/index operators) behind conditional compilation and
BCL polyfills (ReplaceLineEndings, DistinctBy, GetValueOrDefault,
char-based Contains/StartsWith/EndsWith).

Test project drops Verify in favour of plain assertions and checked-in
snapshots so the suite runs on net48/net6.0, with downlevel-compatible
test tooling. CI builds every TFM on Linux and runs net48 on Windows.
The PR for the downlevel re-support targets 5.x, but the workflow only
triggered on push/pull_request to master, so no checks ran. Add 5.x to
both trigger filters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant