Skip to content

Add regeneration instructions to VB Syntax.xml#80703

Merged
jcouv merged 2 commits intomainfrom
copilot/add-xml-doc-comments
Oct 14, 2025
Merged

Add regeneration instructions to VB Syntax.xml#80703
jcouv merged 2 commits intomainfrom
copilot/add-xml-doc-comments

Conversation

Copy link
Contributor

Copilot AI commented Oct 14, 2025

Summary

Fixes an issue where developers editing Syntax.xml and BoundNodes.xml files had no clear instructions on what to do after making changes to regenerate the compiler code.

Problem

When developers modify the XML files that define syntax trees and bound nodes for the compiler, the generated code is not automatically updated. Previously, only three of the four XML files had comments indicating that eng/generate-compiler-code.cmd needs to be run after making changes. The Visual Basic Syntax.xml file was missing this crucial instruction.

Solution

Added an XML comment to src/Compilers/VisualBasic/Portable/Syntax/Syntax.xml instructing developers to run eng/generate-compiler-code.cmd after making changes:

<!-- 
 To re-generate source from this file, run eng/generate-compiler-code.cmd
-->

The comment was placed immediately after the license header, following the same pattern used in:

  • C# Syntax.xml ✓
  • C# BoundNodes.xml ✓
  • VB BoundNodes.xml ✓
  • VB Syntax.xml ✓ (now added)

All four XML files now have consistent documentation for developers.

Fixes #15470

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • 6s7vsblobprodcus313.vsblob.vsassets.io
    • Triggering command: dotnet run --file eng/generate-compiler-code.cs (dns block)
  • 7tjvsblobprodcus341.vsblob.vsassets.io
    • Triggering command: dotnet run --file eng/generate-compiler-code.cs (dns block)
  • lylvsblobprodcus31.vsblob.vsassets.io
    • Triggering command: dotnet run --file eng/generate-compiler-code.cs (dns block)
  • pe3vsblobprodcus354.vsblob.vsassets.io
    • Triggering command: dotnet run --file eng/generate-compiler-code.cs (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Original prompt

This section details on the original issue you should resolve

<issue_title>Compiler code is not updated when Syntax.xml or BoundNodes.xml are changed</issue_title>
<issue_description>And there are no comments in those files giving instructions on what to do when you edit them.

(you have to run build\scripts\generate-compiler-code.cmd)</issue_description>

<agent_instructions>Copilot, can you add to the top of BoundNodes.xml and Syntax.xml some xml doc comments saying you need to run .\eng\generate-compiler-code.cmd after changing these files to properly regenerate things?</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@jcouv Moving to 15.later, as our plate is pretty full at the moment.

Fixes #22331


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: CyrusNajmabadi <4564579+CyrusNajmabadi@users.noreply.github.com>
Copilot AI changed the title [WIP] Add instructions to regenerate compiler code in XML files Add regeneration instructions to VB Syntax.xml Oct 14, 2025
Copilot AI requested a review from CyrusNajmabadi October 14, 2025 14:14
@CyrusNajmabadi CyrusNajmabadi marked this pull request as ready for review October 14, 2025 14:38
@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner October 14, 2025 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Compiler code is not updated when Syntax.xml or BoundNodes.xml are changed

4 participants