VB has the same parsing "bug" as detailed in #57750, but unlike C# it does not support interpolated string handlers, so there are no runtime impacts to the parsing issue. We should update the VB parser to be in sync with the C# parser and the runtime here, but it's not high priority so the team is not going to focus on it. We'd accept a community PR to implement this fix.