Remove generator-produced [Function] definitions for class-based tasks to avoid duplicates with native DF support #585
+75
−149
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.
Azure Functions Durable Extension PR #3229 added native support for class-based orchestrators, activities, and entities. The generator now produces duplicate
[Function]definitions alongside the runtime's, causing potential conflicts.Changes
[Function]attribute generation for class-based tasks (TaskOrchestrator<T>,TaskActivity<T>,TaskEntity<T>) when targeting Durable FunctionsCallMyActivityAsync,ScheduleNewMyOrchestratorInstanceAsync) for type-safe invocation[Function]definitionsBefore
After
Method-based activity triggers (
[ActivityTrigger]on methods) continue generating extension methods as before.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.