title: Visual Studio's CSS Intellisense - Absolute paths & MasterPage files
body: <p>I've noticed that to get CSS-Intellisense working in VS, the paths have to be relative - Is this the case? </p>
  
  <p>However, it seems </p>
  
  <pre><code>&lt;link href="/resources/test.css" [...] /&gt;
  </code></pre>
  
  <p>is far more practical than</p>
  
  <pre><code>&lt;link href="resources/test.css" [...] /&gt;
  </code></pre>
  
  <p>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).</p>
  
  <p>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?</p>
  
  <p>Cheers.</p>
  
  <p>(Note - I'm aware that a &lt;% if (false) { %> type hack is required for user controls)</p>