Add explicit project type configuration for DurableTask source generator #575
+496
−8
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.
The generator auto-detects project type by checking for
Microsoft.Azure.Functions.Worker.Extensions.DurableTaskin referenced assemblies. This fails when transitive dependencies include Functions packages but the project targets Durable Task Worker/Scheduler, causing incorrect code generation (Functions triggers instead ofAddAllGeneratedTasks).Changes
New MSBuild property:
DurableTaskGeneratorProjectTypeoverrides auto-detectionStandalone: Forces standalone Durable Task Worker modeFunctions: Forces Azure Functions modeAutoor omitted: Uses existing auto-detectionImplementation: Read property via
AnalyzerConfigOptionsProviderin generator initialization, check explicit config before falling back to assembly detectionTests: 7 tests covering override scenarios and fallback behavior
Usage
Generates
AddAllGeneratedTasks()registration method:Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.