I am having a problem with a website project in VisualStudio 2005. I set a masterPageFile in the web.config file and then tried to add/work with a content control within the site. Unfortunately, if I don't include a MasterPageFile property in the Page directive, intellisense will not work, design view won't render content (no big deal there, as I rarely use design view), and the content tags and other page items show all kinds of errors. The page compiles ok and displays as expected by applying the MasterPage when I debug, but the best features of the IDE are either unavailable (which is bad) or feeding me incorrect information (which is worse).
Does anyone know if this is just a stupid error on my part? A known bug? I love the idea of a single setting to apply the masterpage to the entire site. The feature is pretty much useless, though, if the development environment doesn't recognize it. I know this isn't a huge deal, as it doesn't require a ton more typing to include the setting in each page instead, and masterpages in general are a terrific addition for ASP.Net. I just like to keep settings like this in as few places as possible to ensure I don't have to dig to replace multiple hidden occurances down the road.