Visual Studio vs VS Code for .NET: one Web API with a slow and a fast endpoint on net10.0 - #2256
Open
vladimir-pecanac-main wants to merge 1 commit into
Conversation
…fast report endpoint
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
1 participant
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.
Adds
visual-studio/VisualStudioVsVsCode, a new folder for the new article "Visual Studio vs VS Code for .NET Developers".A small ASP.NET Core Web API on net10.0 with one slow endpoint (string concatenation in a loop) and one fast endpoint (StringBuilder) that return the same report, plus two xUnit tests. The article opens the same solution in both tools and finds the slow endpoint with Visual Studio's CPU Usage tool and with dotnet-counters and dotnet-trace in VS Code.
dotnet testruns the two tests.The article is not published yet. This PR stays open until the article goes live.