Update documentation for RoslynDeployment startup project and fix outdated references #80716
+14
−11
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 #<issue_number>
Changes
This PR updates the "Building, Debugging and Testing on Windows" documentation to address outdated information and improve clarity around the RoslynDeployment project.
What was fixed:
Removed outdated project reference: The documentation mentioned
Roslyn.VisualStudio.InteractiveComponents
, which no longer exists in the codebase and has been removed.Added explicit setup instructions: The docs now include clear instructions on how to set RoslynDeployment as the startup project: "right-click the RoslynDeployment project in Solution Explorer and select 'Set as Startup Project'".
Clarified what RoslynDeployment is: Added an explanation that RoslynDeployment is a container project located in
src/Deployment
that bundles and deploys all the main Roslyn extensions together, giving developers a complete debugging experience when pressing F5.Fixed incorrect folder paths:
Compilers\Packages
→Compilers\Extension
ExpressionEvaluator\Setup
→ExpressionEvaluator\Package
VisualStudio
→VisualStudio\Setup
Improved formatting: Used bold emphasis on RoslynDeployment for better visibility and restructured the text for better readability.
The documentation already mentioned RoslynDeployment as mentioned in PR #28016, but as noted by @jaredpar, it needed updating to reflect current project structure and provide clearer guidance for contributors.
Original prompt
Fixes #30267
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.