-
Notifications
You must be signed in to change notification settings - Fork 6k
Add missing "To correct this error" content and Error IDs for Visual Basic error documentation #48121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Copilot
wants to merge
7
commits into
main
Choose a base branch
from
copilot/fix-14193
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+64
−0
Conversation
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
…ror documentation files Co-authored-by: BillWagner <493969+BillWagner@users.noreply.github.com>
Copilot finished work on behalf of
BillWagner
August 26, 2025 16:08
BillWagner
reviewed
Aug 27, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments, but then this should be ready.
BillWagner
reviewed
Aug 27, 2025
BillWagner
reviewed
Aug 27, 2025
BillWagner
approved these changes
Aug 27, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now ready
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dotnet-visualbasic/svc
errors-warnings/subsvc
okr-quality
Content-quality KR: Concerns article defects (bugs), freshness, or build warnings.
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.
This PR addresses missing documentation content in 8 Visual Basic error message files that were either completely missing their "To correct this error" sections or were missing the Error ID identifier.
Problem
The following Visual Basic error documentation files had incomplete error correction guidance:
bc36613.md
,bc36614.md
,bc31537.md
,bc31199.md
,bc42207.md
,bc31536.md
- Had empty "To correct this error" sectionsbc30981.md
,bc31538.md
- Were missing both the "Error ID: BCxxxxx" line and had empty correction sectionsSolution
Added comprehensive, actionable correction guidance for all 8 error files:
bc36613.md - Anonymous type member name inference from XML identifiers:
bc31538.md - Member override access modifier conflicts:
bc36614.md - Range variable name inference from XML identifiers in LINQ:
bc31536.md - Friend access denied errors:
And similar comprehensive guidance for the remaining files covering assembly references, friend declarations, .NET Framework updates, and inheritance hierarchy issues.
Validation
Fixes #14193.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Internal previews