Cross-assembly workflow registration#1711
Merged
WhitWaldo merged 3 commits intodapr:masterfrom Feb 14, 2026
Merged
Conversation
…ion csproj that enables the automatic discovery and import of workflows across multiple projects Signed-off-by: Whit Waldo <[email protected]>
Signed-off-by: Whit Waldo <[email protected]>
daanschutte
pushed a commit
to daanschutte/dapr-dotnet-sdk
that referenced
this pull request
Feb 22, 2026
* Added support for a property that can be placed in the entry application csproj that enables the automatic discovery and import of workflows across multiple projects * Added built-in package reference to `Dapr.Workflow.Abstractions` --------- Signed-off-by: Whit Waldo <[email protected]>
WhitWaldo
added a commit
that referenced
this pull request
Feb 23, 2026
#1708) * Readme: Update dapr sidecar launch command Signed-off-by: Daan Schutte <[email protected]> * Readme: swap app start to improve ergonomics Signed-off-by: Daan Schutte <[email protected]> * Delete empty test file Signed-off-by: Daan Schutte <[email protected]> * Add TestActivityException Signed-off-by: Daan Schutte <[email protected]> * Add TestHighCostOrderApproved Signed-off-by: Daan Schutte <[email protected]> * Add TestHighCostOrderApprovalTimeout Signed-off-by: Daan Schutte <[email protected]> * Cleanup Signed-off-by: Daan Schutte <[email protected]> * Update README.md Signed-off-by: Daan Schutte <[email protected]> * Simplified built-in versioning strategies (#1710) * Collapsed available strategies to just Numeric, Date and SemVer and normalized the options between each for similar support. Updated tests accordingly. * Added missing prefix support for date version strategy --------- Signed-off-by: Whit Waldo <[email protected]> * Cross-assembly workflow registration (#1711) * Added support for a property that can be placed in the entry application csproj that enables the automatic discovery and import of workflows across multiple projects * Added built-in package reference to `Dapr.Workflow.Abstractions` --------- Signed-off-by: Whit Waldo <[email protected]> * Removing packages from NuGet publish package list (#1712) * Updating to exclude Dapr.Workflow.Versioning.Abstractions,Dapr.Workflow.Versioning.Generators, and Dapr.Workflow.Versioning.Runtime projects from being deployed to NuGet. * Removed requirement that to discover packages requires a release tag, but left this in place for Publish Packages --------- Signed-off-by: Whit Waldo <[email protected]> * Fix typo Signed-off-by: Daan Schutte <[email protected]> --------- Signed-off-by: Daan Schutte <[email protected]> Signed-off-by: Whit Waldo <[email protected]> Co-authored-by: Whit Waldo <[email protected]>
This was referenced Mar 2, 2026
This was referenced Mar 9, 2026
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
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.
Description
Especially with the introduction of named workflow versioning, there may exist a desire to maintain workflows in a separate assembly to the one actually executing, but the automatic workflow discovery used in the source generator didn't support this - now it does.
By default, this functionality is disabled as it does impose a penalty to build time (because it has to search through all referenced assemblies for any
Workflow<,>implementations), but if you wish to opt into such support, add the following to your .csproj of your executing application:At build time, this will result in the source generator adding any and all workflow implementations it discovers to the registry it maintains for internal version tracking.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: