Hi fellow programmers and nerds!

When creating regular expressions Visual Studio, the IDE will highlight the string if it's preceded by a verbatim identifier (for example, `@"Some string`). This looks something like this:

[![A screenshot of the highlighting](https://i.stack.imgur.com/dzCKs.png)](https://i.stack.imgur.com/dzCKs.png)

(Notice the way the string is highlighted). Most of you will have seen this by now, I'm sure.

My problem: I am using a package acquired from NuGet which deals with regular expressions, and they have a function which takes in a regular expression string, however their function doesn't have the syntax highlighting.

[![the function without highlighting](https://i.stack.imgur.com/SR8fc.png)](https://i.stack.imgur.com/SR8fc.png)

As you can see, this just makes reading the Regex string just a pain. I mean, it's not all-too-important, but it would make a difference if we can just have that visually-helpful highlighting to reduce the time and effort one's brain uses trying to decipher the expression, especially in a case like mine where there will be quite a quantity of these expressions.

**The question**

So what I'm wanting to know is, is there a way to make a function highlight the string this way\*, or is it just something that's hardwired into the IDE for the specific case of the Regex c-tor? Is there some sort of annotation which can be tacked onto the function to achieve this with minimal effort, or would it be necessary to use some sort of extension?

\*I have wrapped the call to `AddStyle()` into one of my own functions anyway, and the string will be passed as a parameter, so if any modifications need to be made to achieve the syntax-highlight, they can be made to my function. Therefore the fact that the `AddStyle()` function is from an external library should be irrelevant.

If it's a lot of work then it's not worth my time, somebody else is welcome to develop an extension to solve this, but if there is a way...

**Important distinction**

Please bear in mind I am talking about Visual Studio, *NOT* Visual Studio Code.

Also, if there is a way to pull the original expression string from the Regex, I might do it that way, since performance isn't a huge concern here as this is a once-on-startup thing, however I would *prefer* not to do it that way. I don't actually need the Regex object.