Instructions to use SQL Server for opt concurrency #34453
Merged
Conversation
This file contains 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.
Fixes #33943
Thanks @crazyfox55! 🚀 ... You can follow the instructions on the diff to convert the app to use SQL Server to demo the concurrency implementation with the native concurrency tokens. I don't want to convert the entire sample over to this because SQL Server isn't as widely supported as SQLite. I also don't want to have to place full .NET CLI guidance for this scenario. Most devs using SQL Server are working in VS, so only having VS guidance should be ok for this.
I'll leave this up until tomorrow (Thursday) morning to give you some time to look at it. I also like to sleep on a PR 🛌💤 and make final touch-up changes in the morning before merging it.
Internal previews