Here is today's special question. When using Code as my template editor, the Problems tab appears to complain about some uses of <%= tags , and I'm trying to figure out the pattern. For example, the message related to the bit shown below is property value expected css(css-propertyvalueexpected)

Is there some magic trick with Code to teach it to understand the framework injection tags as legitimate syntax? Or is there actually something bad here that does not appear to manifest in any way in the generated page?
TIA
No the tags are not standard HTML so they will not show as special characters and usually cause problems when embedded inside of strings because they're not encoded.
Outside of string embedding it works reasonably well because they'll just show as HTML tags.

This is using the standard Html view. To me that looks pretty acceptable - in fact I like that it highlights the starting tag so you can see them in the code even if the closing tag is not highlighted.
You can also install the Classic ASP syntax extension which will basically hide the tags as text. There are others that might work better at highlighting but remember that anything that really does ASP classic would expect VB script code in between and then you run into issues with the code flagging for errors.
Personally I just use the default Html view which is what's in my screen shot.
Forgive the n00b question but I don't see a "standard HTML view" option in VC? Anyway, Friday evening and it's time to call it a day. Thanks again!
You can apply a syntax to files and extensions. The syntax settings are in the control palette or you can click on the status bar lower right - there's a syntax item. When you pick you also get options to map an unknown file extension in the menu drop down that comes up and you can pick Html there or ASP Classic if you installed that.
+++ Rick --
Ah! I see that now. It's already set to HTML. I shall continue to ignore the Problems output.
The problems output will always give you issues, because the view doesn't understand the expressions embedded. You can choose Handle Bars and that might ignore what's between the {{ }} brackets.