Update project to target .NET 8.0 and .NET 10 and upgrade dependencies by torosent · Pull Request #510 · microsoft/durabletask-dotnet

torosent · 2025-11-21T21:11:42Z

This pull request upgrades the project to support .NET 8.0 and .NET 10.0, modernizes dependencies across the codebase, and refactors the source generator for improved performance and maintainability. The most important changes are grouped below.

.NET Version Upgrades and Multi-Targeting

Updated build and workflow configuration to use .NET 8.0 in .github/workflows/validate-build.yml and set the default SDK to .NET 10.0 in global.json.
Changed project files for all samples and main libraries to target multiple frameworks, including net6.0, net8.0, and net10.0 where appropriate. This ensures compatibility and future-proofs the codebase.

Dependency Updates

Upgraded package versions for Microsoft.Extensions., Azure., Grpc., Microsoft.CodeAnalysis., and other libraries in Directory.Packages.props to their latest releases compatible with .NET 8.0/10.0. This improves security, performance, and feature support.
Updated testing and analysis dependencies (e.g., BenchmarkDotNet, xunit, FluentAssertions) to latest versions for improved reliability and compatibility.

Build and Development Environment

Updated VS Code task configuration to use the net8.0 output directory for Azure Functions, aligning with the new target frameworks.

Source Generator Refactor

Refactored DurableTaskSourceGenerator to use the incremental generator API (IIncrementalGenerator), improving performance and reliability of code generation. The new implementation uses Roslyn incremental providers and removes the legacy syntax receiver pattern.

General Code Modernization

Added System.Collections.Immutable import in the generator for modern collection handling.

Copilot

Pull request overview

This PR upgrades the project from .NET 6.0 to .NET 8.0, updating all project files, dependencies, tooling configurations, and migrating source generators to use the incremental generator API. The migration enables access to .NET 8's long-term support, security improvements, and new features while maintaining backward compatibility through multi-targeting.

Key changes:

Updated all project target frameworks from net6.0 to net8.0, with multi-targeted projects now including net8.0 alongside netstandard2.0 and net48
Upgraded dependencies to .NET 8-compatible versions including Microsoft.Extensions., Azure., Grpc, and testing packages
Migrated source generator from ISourceGenerator to IIncrementalGenerator API for better performance and compatibility with .NET 8 tooling

Reviewed changes

Copilot reviewed 34 out of 34 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
test/Worker/Grpc.Tests/Worker.Grpc.Tests.csproj	Updated target frameworks from `net6.0;net48` to `net8.0;net48` and conditional package reference condition
test/Worker/Core.Tests/Worker.Tests.csproj	Updated target framework from `net6.0` to `net8.0`
test/Worker/AzureManaged.Tests/Worker.AzureManaged.Tests.csproj	Updated target framework from `net6.0` to `net8.0`
test/TestHelpers/TestHelpers.csproj	Added `net8.0` to multi-target frameworks alongside `net6.0;netstandard2.0`
test/Shared/AzureManaged.Tests/Shared.AzureManaged.Tests.csproj	Updated target framework from `net6.0` to `net8.0`
test/ScheduledTasks.Tests/ScheduledTasks.Tests.csproj	Updated target framework from `net6.0` to `net8.0` and removed explicit Microsoft.NET.Test.Sdk reference
test/Grpc.IntegrationTests/OrchestrationPatterns.cs	Added explicit cast to fix compilation issue with Assert.Equal generic method resolution
test/Grpc.IntegrationTests/Grpc.IntegrationTests.csproj	Updated target framework from `net6.0` to `net8.0`
test/Generators.Tests/Utils/TestHelpers.cs	Changed generic constraint from `ISourceGenerator` to `IIncrementalGenerator` and minor formatting fix
test/Generators.Tests/Utils/CSharpSourceGeneratorVerifier.cs	Updated generic constraint and reference assemblies from .NET 6.0 to .NET 8.0
test/Generators.Tests/Generators.Tests.csproj	Updated target framework from `net6.0` to `net8.0`
test/Client/OrchestrationServiceClientShim.Tests/Client.OrchestrationServiceClientShim.Tests.csproj	Updated target framework from `net6.0` to `net8.0`
test/Client/Grpc.Tests/Client.Grpc.Tests.csproj	Updated target frameworks from `net6.0;net48` to `net8.0;net48`
test/Client/Core.Tests/Client.Tests.csproj	Updated target framework from `net6.0` to `net8.0`
test/Client/AzureManaged.Tests/Client.AzureManaged.Tests.csproj	Updated target framework from `net6.0` to `net8.0`
test/Benchmarks/Benchmarks.csproj	Updated target framework from `net6.0` to `net8.0`
test/Analyzers.Tests/Analyzers.Tests.csproj	Updated target framework from `net6.0` to `net8.0`
test/Abstractions.Tests/Abstractions.Tests.csproj	Updated target framework from `net6.0` to `net8.0`
src/Worker/Grpc/Worker.Grpc.csproj	Updated target frameworks from `netstandard2.0;net6.0` to `netstandard2.0;net8.0`
src/Worker/AzureManaged/Worker.AzureManaged.csproj	Updated target framework from `net6.0` to `net8.0`
src/ScheduledTasks/ScheduledTasks.csproj	Updated target framework from `net6.0` to `net8.0`
src/InProcessTestHost/InProcessTestHost.csproj	Updated target framework from `net6.0` to `net8.0`
src/Grpc/Grpc.csproj	Updated target frameworks from `netstandard2.0;net6.0` to `netstandard2.0;net8.0` and conditional package reference condition
src/Generators/DurableTaskSourceGenerator.cs	Migrated from `ISourceGenerator` to `IIncrementalGenerator` API with complete rewrite of initialization and execution logic
src/Extensions/AzureBlobPayloads/AzureBlobPayloads.csproj	Updated target frameworks from `netstandard2.0;net6.0` to `netstandard2.0;net8.0`
src/Client/Grpc/Client.Grpc.csproj	Updated target frameworks from `netstandard2.0;net6.0` to `netstandard2.0;net8.0`
src/Client/AzureManaged/Client.AzureManaged.csproj	Updated target framework from `net6.0` to `net8.0`
samples/WebAPI/WebAPI.csproj	Updated target framework from `net6.0` to `net8.0`
samples/ScheduleWebApp/ScheduleWebApp.csproj	Updated target framework from `net6.0` to `net8.0`
samples/AzureFunctionsApp/AzureFunctionsApp.csproj	Updated target framework from `net6.0` to `net8.0`
global.json	Updated .NET SDK version from 8.0.100 to 8.0.416
Directory.Packages.props	Updated all package versions to .NET 8-compatible versions
.vscode/tasks.json	Updated output path from `net6.0` to `net8.0` for Azure Functions task
.github/workflows/validate-build.yml	Updated workflow to use .NET 8.0 instead of .NET 6.0

test/Generators.Tests/Utils/TestHelpers.cs

Copilot · 2025-11-21T21:15:12Z

test/TestHelpers/TestHelpers.csproj


  <PropertyGroup>
-    <TargetFrameworks>net6.0;netstandard2.0</TargetFrameworks>
+    <TargetFrameworks>net8.0;net6.0;netstandard2.0</TargetFrameworks>


[nitpick] The target frameworks should be ordered from most specific to most general. The current order net8.0;net6.0;netstandard2.0 is correct, but since this is a shared test helper library, keeping net6.0 may not be necessary if all test projects are now targeting net8.0. Consider removing net6.0 to simplify the build matrix unless backward compatibility with .NET 6 test projects is explicitly required.

@copilot open a new pull request to apply changes based on this feedback

Copilot · 2025-11-21T21:17:20Z

@torosent I've opened a new pull request, #511, to work on those changes. Once the pull request is ready, I'll request review from you.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot

Pull request overview

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

* Initial plan * Remove net6.0 target from TestHelpers.csproj Co-authored-by: torosent <17064840+torosent@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: torosent <17064840+torosent@users.noreply.github.com>

…urabletask-dotnet into torosent/update-net8

Copilot

Pull request overview

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

halspang · 2025-11-21T22:05:51Z

@jviau - I tried this change a while back and you flagged it as a breaking change. Do you know if we've updated/what we need to update to be able to do this?

jviau · 2025-11-21T22:15:38Z

Dropping net6.0 TFM will introduce a breaking change to net6.0 customers. And a potentially obscure / difficult to identify one at that. Since these projects all multi-target netstandard2.0 as well, net6.0 customers won't outright fail restore. They will be silently shifted to netstandard2.0 and their entire transitive dependency graph as well as a result. This can be very harmful to those customers. Especially the change in Grpc dependencies: these customers will be moved from Grpc.Net.Client to Grpc.Core, which is unsupported and a much worse option that Grpc.Net.Client.

There are a couple options to supporting net8.0:

Do not remove net6.0. Just add net8.0 in addition to net6.0 (might as well add net10.0 while you are at it)
- this is by far the easiest and least disruptive option.
- net6.0 can then be removed in a major version rev.
Remove net6.0 but add targets to explicit break the customers build, telling them net6.0 is out of support and cannot be used with these packages anymore.
- This is fairly disruptive. Will also need to block net7.0 as well. Dotnet BCL libraries started in net10 (or is it net9?) include targets that warn when you use them in out of support TFMs. I would go with an error though here as it is more impactful than the dotnet BCL case, they are just warning it isn't tested. In our case it is an outright massive behavior change / break, but one that can manifest only at runtime. Failing at build time would be much preferred.

Regardless of the choice made, I recommend also adding net10.0 as it is LTS. I would then condition the packages in Directory.Packages.props to be 8.x or 10.x based on the TFM. If you do keep net6.0, I think it is acceptable to still bump all net6.0 dependencies to 8.x. So you would have: netstandard2.0, net6.0, net8.0 --> 8.x dependencies. net10.0 --> 10.x dependencies.

Copilot

Pull request overview

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

torosent · 2025-11-21T23:41:41Z

Dropping net6.0 TFM will introduce a breaking change to net6.0 customers. And a potentially obscure / difficult to identify one at that. Since these projects all multi-target netstandard2.0 as well, net6.0 customers won't outright fail restore. They will be silently shifted to netstandard2.0 and their entire transitive dependency graph as well as a result. This can be very harmful to those customers. Especially the change in Grpc dependencies: these customers will be moved from Grpc.Net.Client to Grpc.Core, which is unsupported and a much worse option that Grpc.Net.Client.

There are a couple options to supporting net8.0:

Do not remove net6.0. Just add net8.0 in addition to net6.0 (might as well add net10.0 while you are at it)

this is by far the easiest and least disruptive option.

net6.0 can then be removed in a major version rev.

Remove net6.0 but add targets to explicit break the customers build, telling them net6.0 is out of support and cannot be used with these packages anymore.

This is fairly disruptive. Will also need to block net7.0 as well. Dotnet BCL libraries started in net10 (or is it net9?) include targets that warn when you use them in out of support TFMs. I would go with an error though here as it is more impactful than the dotnet BCL case, they are just warning it isn't tested. In our case it is an outright massive behavior change / break, but one that can manifest only at runtime. Failing at build time would be much preferred.

Regardless of the choice made, I recommend also adding net10.0 as it is LTS. I would then condition the packages in Directory.Packages.props to be 8.x or 10.x based on the TFM. If you do keep net6.0, I think it is acceptable to still bump all net6.0 dependencies to 8.x. So you would have: netstandard2.0, net6.0, net8.0 --> 8.x dependencies. net10.0 --> 10.x dependencies.

Thanks Jacob. I updated to support 6.0, 8.0 and 10.0

halspang

Minor comments/questions. Overall looks good!

samples/AzureFunctionsApp/AzureFunctionsApp.csproj

samples/AzureFunctionsUnitTests/AzureFunctionsApp.Tests.csproj

src/Generators/DurableTaskSourceGenerator.cs

…compatibility The Azure Functions host process runs on net8.0 and loads DurableTask extension assemblies into its process. Packages like Microsoft.Extensions.*, Bcl.AsyncInterfaces, and System.Text.Json are part of the .NET shared framework - the host only provides version 8.0.0.0 of these assemblies. PR #510 upgraded these to 10.x, which causes FileNotFoundException at runtime: Could not load file or assembly 'Microsoft.Extensions.Options, Version=10.0.0.0' This reverts the 11 shared-framework packages to 8.x while keeping all other dependency upgrades (Grpc, Protobuf, Azure.Storage.Blobs, Azure.Identity, etc). Packages reverted: - Microsoft.Extensions.* (9 packages): 10.0.2 -> 8.x - Microsoft.Bcl.AsyncInterfaces: 10.0.2 -> 8.0.0 - System.Text.Json: 10.0.2 -> 8.0.5 Test project fix: - Generators.Tests: VersionOverride for DependencyInjection (net10 test project needs 10.x via Functions.Worker transitive dep, safe since tests don't load into the Functions host) global.json: relaxed SDK version to match installed 10.0.104

torosent added 2 commits November 21, 2025 13:00

Update project to target .NET 8.0 and upgrade dependencies

2abefaa

Updated generators

59461f2

Copilot AI review requested due to automatic review settings November 21, 2025 21:11

Copilot started reviewing on behalf of torosent November 21, 2025 21:12 View session

Copilot finished reviewing on behalf of torosent November 21, 2025 21:14

Copilot AI reviewed Nov 21, 2025

View reviewed changes

torosent requested a review from halspang November 21, 2025 21:16

Copilot AI mentioned this pull request Nov 21, 2025

Remove net6.0 target from TestHelpers #511

Merged

Update test/Generators.Tests/Utils/TestHelpers.cs

b5301a1

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot AI review requested due to automatic review settings November 21, 2025 21:17

Copilot started reviewing on behalf of torosent November 21, 2025 21:17 View session

Copilot finished reviewing on behalf of torosent November 21, 2025 21:20

Copilot AI reviewed Nov 21, 2025

View reviewed changes

Copilot AI and others added 3 commits November 21, 2025 13:23

update

99f4d8a

Merge branch 'torosent/update-net8' of https://github.com/microsoft/d…

117d985

…urabletask-dotnet into torosent/update-net8

Copilot AI review requested due to automatic review settings November 21, 2025 21:34

Copilot started reviewing on behalf of torosent November 21, 2025 21:34 View session

Copilot finished reviewing on behalf of torosent November 21, 2025 21:37

Copilot AI reviewed Nov 21, 2025

View reviewed changes

update grpc

d7d4c76

torosent added 2 commits November 21, 2025 15:30

Update project files to support .NET 10.0 alongside .NET 6.0 and 8.0

26aaecd

update

bd84248

Copilot AI review requested due to automatic review settings November 21, 2025 23:30

torosent changed the title ~~Update project to target .NET 8.0 and upgrade dependencies~~ Update project to target .NET 8.0 and .NET 10 and upgrade dependencies Nov 21, 2025

Copilot started reviewing on behalf of torosent November 21, 2025 23:31 View session

update build

fee3837

Copilot finished reviewing on behalf of torosent November 21, 2025 23:34

Copilot AI reviewed Nov 21, 2025

View reviewed changes

halspang reviewed Nov 21, 2025

View reviewed changes

samples/AzureFunctionsApp/AzureFunctionsApp.csproj Show resolved Hide resolved

samples/AzureFunctionsUnitTests/AzureFunctionsApp.Tests.csproj Show resolved Hide resolved

src/Generators/DurableTaskSourceGenerator.cs Show resolved Hide resolved

halspang approved these changes Nov 22, 2025

View reviewed changes

torosent merged commit 095253f into main Nov 22, 2025
4 checks passed

torosent deleted the torosent/update-net8 branch November 22, 2025 00:35

dependabot bot mentioned this pull request Dec 8, 2025

[nuget][Find]- Bump Microsoft.DurableTask.Client from 1.17.1 to 1.18.0 DFE-Digital/single-unique-identifier#247

Closed

dependabot bot mentioned this pull request Dec 22, 2025

[nuget][Find]- Bump Microsoft.DurableTask.Client from 1.17.1 to 1.18.1 DFE-Digital/single-unique-identifier#328

Closed

dependabot bot mentioned this pull request Jan 26, 2026

[nuget][Find]- Bump Microsoft.DurableTask.Client from 1.17.1 to 1.19.1 DFE-Digital/single-unique-identifier#368

Closed

dependabot bot mentioned this pull request Feb 3, 2026

[nuget][Find]- Bump Microsoft.DurableTask.Client from 1.17.1 to 1.20.1 DFE-Digital/single-unique-identifier#391

Closed

YunchuWang mentioned this pull request Apr 3, 2026

fix: revert shared framework packages to 8.x for net8 Functions host compatibility #698

Merged

Conversation

torosent commented Nov 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Copilot AI Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

torosent Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Nov 21, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

halspang commented Nov 21, 2025

Uh oh!

jviau commented Nov 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

torosent commented Nov 21, 2025

Uh oh!

halspang left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

torosent commented Nov 21, 2025 •

edited

Loading

jviau commented Nov 21, 2025 •

edited

Loading