I hope someone can help me with this annoyance.
At work, we have two independent website designs that share a common MasterPage. MasterPage is built into the class library, which references both projects. We use our own VirtualPathProvider, which allows us to reference MasterPage in each project. This works fine at runtime / compilation, but it breaks intellisense inside the aspx page markup.
When I set the MasterPageFile property to "~ / EmbeddedMasterPage.Master", Visual Studio shows a red squiggley error below it saying "Path not found", with a directory indicating that it is trying to find this file inside the website project (unlike class library project). Since Visual Studio cannot figure out where MasterPage is located, this causes all intellisense to break. It will not show anything for tags. In fact, the only intellisense he will give me is the basic html tags. From Googling around, the only information I could find is that VS cannot find the html / head / body root tags in the built-in MasterPage. I could not find a way to fix this.
This happens both in Visual Studio 2008 and in 2010.
Update (4/10/2011)
, . /, .