antic
Perch
Hey all.
If anyone has experience with modifying VS Intellisense schemas, I'd appreciate some advice.
I use VS'05 to develop in both ASP.NET and classic ASP. But it annoys me how VS's intellisense is, on the one hand, so useful and yet, on the other, so anal about "correct" xhtml that it becomes a pain.
In classic ASP, those little red wiggly lines appear under every element that needs be in a parent element (ie. everything under the html tag) because VS doesn't like the way classic ASP outputs disjointed html snippets.
So far, I've worked out how to customise an Intellisense schema for use with VS and classic ASP which loosens up a lot of things, using the quick guide found here. Very useful info - I've created a "custom" XHTML schema for my ASP coding.
But try as I might, I can't get rid of those "must be inside a parent element" notations. Can't seem to find any reference to that particular issue within the schemas.
Anyone have any extra knowledge about this?
Cheers!
If anyone has experience with modifying VS Intellisense schemas, I'd appreciate some advice.
I use VS'05 to develop in both ASP.NET and classic ASP. But it annoys me how VS's intellisense is, on the one hand, so useful and yet, on the other, so anal about "correct" xhtml that it becomes a pain.
In classic ASP, those little red wiggly lines appear under every element that needs be in a parent element (ie. everything under the html tag) because VS doesn't like the way classic ASP outputs disjointed html snippets.
So far, I've worked out how to customise an Intellisense schema for use with VS and classic ASP which loosens up a lot of things, using the quick guide found here. Very useful info - I've created a "custom" XHTML schema for my ASP coding.
But try as I might, I can't get rid of those "must be inside a parent element" notations. Can't seem to find any reference to that particular issue within the schemas.
Anyone have any extra knowledge about this?
Cheers!