Dear Microsoft Gods,

Maybe I'm spoiled with my background compilation in VB.net, but you got me hooked.  I was a lost little boy on the playground and you approached me all decked out in your bad leather jacket and offered me the candy.  So now I beg you:  Please fix intellisense.  I don't want it to work some of the time.  I want it to work all the time.  I especially want it to work with master pages. 

I've been moving repeated control declarations into my web.config, as noted here.  And I even went ahead and

set my masterpage in there as well:

So tell me why, then, would switching into design view on a page:

<%@ Page Language="vb" AutoEventWireup="false" Inherits="loginpage" CodeFile="login.aspx.vb" CodeFileBaseClass="pageclass" %>

give me:

Apparently, this has been this way for a while: http://blogs.ipona.com/davids/archive/2005/10/12/3408.aspx.

And Don't get me wrong: I'm grateful for the MasterType directive in order to type Master.FooterText="Hey Now!"

(MSDN:

To provide access to members of the master page, the Page class exposes a Master property. To access members of a specific master page from a content page, you can create a strongly typed reference to the master page by creating a @ MasterType directive. The directive allows you to point to a specific master page. When the page creates its Master property, the property is typed to the referenced master page.)

But I really want to put that in web.config as well - whats the point of centralizing just a few directives and registrations and not all of them.  You gotta figure that most content pages are going to want to easily talk to their master page.   So if that's not already being addressed, please do so.  Thanks!  Looking forward to the release!

-Dave