Improve Guidance on when to use Sync/Async Nexus Operations - #200
Merged
Conversation
Quinn-With-Two-Ns
approved these changes
Jul 28, 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
2 participants
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.
What was changed
Improved the NexusSimple sample to highlight when to use Synchronous vs Asynchronous Nexus Operations. Feedback on the nexus dotnet sdk told us that this was not clear enough. So we are improving this in our examples and documentation. The sample now clearly describes when to use sync or async.
Why?
This was requested feedback from users of the dotnet sdk
Checklist
Closes
How was this tested:
Tested locally, samples still work when running locally now.
Any docs updates needed?