Visual Studio's CSS Intellisense - Absolute paths & MasterPage files
Posted
by Overflew
on Stack Overflow
See other posts from Stack Overflow
or by Overflew
Published on 2009-07-08T23:21:04Z
Indexed on
2010/03/29
19:03 UTC
Read the original article
Hit count: 386
intellisense
|css
Hi there.
I've noticed that to get CSS-Intellisense working in VS, the paths have to be relative - Is this the case?
However, it seems
<link href="/resources/test.css" [...] />
is far more practical than
<link href="resources/test.css" [...] />
I'm including the CSS in the master page, and don't see much good in including it as a content block, just to get the relative paths correct for each directory depth. I've had a quick try with inline code resolving the path, but no dice there either (for Intellisense).
I feel I'm missing something fairly simple - What's the correct approach here to have CSS Intellisense work across the pages in the app during dev, and render fine in any deployed state?
Cheers.
(Note - I'm aware that a <% if (false) { %> type hack is required for user controls)
© Stack Overflow or respective owner