Skip to content

Support multi-targeting for .NET 8, 9, and 10 with version updates#14

Merged
linckez merged 3 commits intomainfrom
feature/multi-target-net8-net9-net10
Apr 1, 2026
Merged

Support multi-targeting for .NET 8, 9, and 10 with version updates#14
linckez merged 3 commits intomainfrom
feature/multi-target-net8-net9-net10

Conversation

@linckez
Copy link
Copy Markdown
Owner

@linckez linckez commented Apr 1, 2026

This pull request updates the project files to support multiple .NET target frameworks (net8.0, net9.0, net10.0), introduces framework-specific dependencies for better compatibility, and bumps package versions across several projects.

Multi-targeting and Dependency Management:

  • Updated BlazorLocalization.Extensions.csproj and BlazorLocalization.TranslationProvider.Crowdin.csproj to target net8.0, net9.0, and net10.0 instead of only net10.0. This improves compatibility with a wider range of .NET versions. [1] [2]
  • Refactored Microsoft.Extensions package references in both projects to use framework-specific versions via conditional ItemGroups, ensuring each target framework references the correct package versions. [1] [2]

Other Project Updates:

  • Set LangVersion to 14 in the multi-targeted projects to align with the latest C# language features. [1] [2]
  • Bumped package versions: BlazorLocalization.Extensions to 10.3.0, BlazorLocalization.TranslationProvider.Crowdin to 10.1.0, and BlazorLocalization.Extractor tool to 10.1.3. [1] [2] [3]

Copilot AI and others added 3 commits April 1, 2026 12:47
- Both library projects now produce assemblies for all three frameworks
- Microsoft.Extensions.* deps are version-matched per TFM (8.x/9.x/10.x)
- Common deps (SmartFormat.NET, FusionCache) already support all targets
- LangVersion=preview enables C# 14 features (extension blocks) on all TFMs
- Extractor CLI stays net10.0 only (not a library NuGet)
- All 145 tests pass, NuGet pack verified

Agent-Logs-Url: https://github.com/linckez/BlazorLocalization/sessions/a56d0ca1-5cc4-47c6-b175-00f07f67fe8f

Co-authored-by: linckez <10991491+linckez@users.noreply.github.com>
- BlazorLocalization.Extensions: 10.2.1 → 10.3.0
- BlazorLocalization.TranslationProvider.Crowdin: 10.0.3 → 10.1.0
- BlazorLocalization.Extractor: 10.1.2 → 10.1.3

Agent-Logs-Url: https://github.com/linckez/BlazorLocalization/sessions/4812f4c1-8fb2-4dee-b431-3ba7e7c4b5ed

Co-authored-by: linckez <10991491+linckez@users.noreply.github.com>
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR expands library compatibility by multi-targeting net8.0, net9.0, and net10.0 in key packages, while updating package/tool versions and aligning compiler settings (C# LangVersion 14) to support the broader target matrix.

Changes:

  • Multi-target BlazorLocalization.Extensions and BlazorLocalization.TranslationProvider.Crowdin for net8.0;net9.0;net10.0.
  • Switch Microsoft.Extensions dependencies to framework-conditional PackageReference groups for version alignment per TFM.
  • Bump package/tool versions for the affected projects.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
src/BlazorLocalization.Extensions/BlazorLocalization.Extensions.csproj Multi-targets net8/9/10, sets C# 14, and uses TFM-conditional Microsoft.Extensions package references.
src/BlazorLocalization.TranslationProvider.Crowdin/BlazorLocalization.TranslationProvider.Crowdin.csproj Multi-targets net8/9/10, sets C# 14, and uses TFM-conditional Microsoft.Extensions package references.
src/BlazorLocalization.Extractor/BlazorLocalization.Extractor.csproj Bumps the extractor tool version to 10.1.3.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@linckez linckez merged commit 1eb09de into main Apr 1, 2026
8 checks passed
@linckez linckez deleted the feature/multi-target-net8-net9-net10 branch April 1, 2026 14:10
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.

3 participants