Add .NET 10 support and update package references - #441
Open
KAJOOSH wants to merge 6 commits into
Open
Conversation
Add net10.0 target framework support across Parbad core, ASP.NET Core integration, storage packages, gateway packages, and test projects. Update package references to current stable versions where compatible, while keeping netstandard2.0/netstandard2.1-specific ASP.NET Core and Microsoft.Extensions dependencies on the 2.2 line to preserve legacy consumer compatibility. Use conditional EF Core package references so legacy EntityFrameworkCore storage targets stay on the latest compatible 5.0 patch release and net10.0 uses EF Core 10. Add direct compatibility/security overrides for vulnerable transitive dependencies without moving legacy netstandard dependency groups to modern-only package lines. Update test package references, make previously non-discoverable gateway/core tests executable, and adjust tests for MSTest 4 behavior and net10.0 runtime expectations. Fix net10.0 build issues in cache and Entity Framework Core storage tests, use IWebHostEnvironment for modern ASP.NET Core targets, and remove obsolete test-helper storage usage. Validated with dotnet restore, dotnet build, dotnet test, and vulnerable package checks across all project files.
Bump version numbers across all Parbad projects for the v3.12.0 release. Update <PackageReleaseNotes> URLs in .csproj files to reference the new release notes. No functional or code changes included; metadata only.
Add a single multi-targeted framework compatibility test project that runs against every supported .NET Core runtime target from netcoreapp3.0 through net10.0. The project acts as one shared test point for runtime compatibility instead of maintaining separate test projects per framework version. The tests assert that the executing target framework is part of the supported runtime matrix and verify that each runtime-compatible Parbad project assembly can be loaded for that target. Entity Framework Core storage is included only for net5.0 and later because that package does not target netcoreapp3.x. Package references are conditioned by target framework so older runtimes use compatible MSTest/Test SDK assets while net8.0 and newer use the current MSTest 4 stack. The solution file includes the new test project under the existing test solution folder so dotnet test Parbad.sln runs the full compatibility matrix. Reason: this provides an explicit regression check that future target framework or package updates keep the declared .NET Core support matrix buildable and testable. Validated with dotnet restore Parbad.sln, dotnet build tests/Parbad.FrameworkCompatibility.Tests/Parbad.FrameworkCompatibility.Tests.csproj --no-restore -v:q, dotnet test tests/Parbad.FrameworkCompatibility.Tests/Parbad.FrameworkCompatibility.Tests.csproj --no-build --no-restore, and dotnet test Parbad.sln --no-build --no-restore.
Upgraded the UseDotNet@2 task in azure-pipelines.yml to use .NET SDK version 10.x instead of 9.x for builds.
Refactored pipeline YAML to use .NET SDK 10.0.x, added .NET SDK info step, and standardized usage of variables. Optimized restore, build, test, and pack steps with '--no-restore' and '--no-build' flags for better efficiency. Improved formatting and task display names for clarity.
Added UseDotNet@2 tasks to install .NET SDKs from 3.0 to 10.0 with explicit installation paths. Enhanced the script step to show detailed SDK and runtime info. Increased test output verbosity by adding --verbosity normal to the test step.
Contributor
Author
|
The reason for updating This project targets multiple .NET versions, from The pipeline was also updated to use After applying these changes, the issue was resolved and |
Contributor
Author
|
Hello |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This pull request adds .NET 10 support across the Parbad solution and prepares the packages for the v3.12.0 release.
It updates target frameworks, package references, release metadata, and test projects while preserving compatibility with existing legacy targets. It also adds a dedicated multi-targeted framework compatibility test project to make sure Parbad remains buildable and loadable across the supported .NET runtime matrix.
What changed
.NET 10 support
net10.0target framework support across:Package reference updates
netstandard2.0/netstandard2.1dependency groups on compatible ASP.NET Core and Microsoft.Extensions package lines to avoid breaking older consumers.net10.0targets use EF Core 10.Test updates
ASP.NET Core compatibility
IWebHostEnvironmentwhere appropriate, while keeping compatibility with older hosting abstractions.Release metadata
<PackageReleaseNotes>links in project files to point to the v3.12.0 release notes.Cross-framework compatibility tests
Added a new multi-targeted test project:
tests/Parbad.FrameworkCompatibility.TestsThe new test project targets the supported runtime matrix from
netcoreapp3.0throughnet10.0.It verifies that:
Entity Framework Core storage compatibility checks are included only for
net5.0and later, because that package does not targetnetcoreapp3.x.Added the new compatibility test project to
Parbad.slnso it runs as part of the full solution test suite.Why
.NET 10 support requires updating target frameworks, package references, test dependencies, and a few compatibility-specific code paths.
The new compatibility test project provides a regression safety net for future framework/package updates, ensuring the declared Parbad runtime support matrix remains buildable and testable.
Validation
The changes were validated with: