Issue with regex and VS 2022

Question

0.00/5 (No votes)

See more:

2022

I've been using the same Regex pattern since VS 2017 for a spell checker. But one of several issues with VS 2022 is that the same pattern generates errors in my VB code. The pattern is:

Dim ptrn as string = "\b[a-zA-Z0-9]{1,}['’-]{0,}[a-zA-Z0-9]{0,}\b|b\w+[\.\,\?\!]\w+\b"

The purpose of the pattern is to detect each word in a text doc including hyphenated words and English contractions. Error messages include "b is not declared" and "missing braces."

I am assuming this is something to do with a setting is VS 2022 I don't know about. Any info is greatly appreciated.

What I have tried:

Tried breaking up the string and replacing the apostrophes with chrw(27).

Posted 4-Sep-24 11:23am

Alan Burkhart

Add a Solution

Comments

CPallini 5-Sep-24 3:36am

You could mark it as 'solved' or even delete it.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Alan Burkhart · Answer 1 · 2024-09-04T12:00:00

Solution 1

OK never mind I found it. It was a misplaced quote in a line of code above this one. No error msg, no red line, nothing.

Posted 4-Sep-24 12:00pm

Alan Burkhart

Comments

Richard Deeming 9-Sep-24 4:47am

VB.NET has supported multi-line strings since VS2015. As a result, if you don't close a string on a previous line, it's not an error; the string just keeps going until the next quote character. The errors will then appear with the contents of that string, when the compiler tries to interpret them as code.