@Register and MasterPage

[bryanp10]

Why does the @Register directive not carry over into templated pages?
I have to @Register the user controls I want to use on every page...
this seems contrary to the whole point of master pages to begin
with. ????

 

[Mark Rae]

Why does the @Register directive not carry over into templated pages?
I have to @Register the user controls I want to use on every page...
this seems contrary to the whole point of master pages to begin
with. ????

One of the major misconceptions with MasterPages is that they are somehow
the ASP.NET 2 equivalent of framesets - they aren't at all...

MasterPages are nothing more than UserControls...

When you add a MasterPage to a content page, you are just adding a
UserControl - the content page is the "main" page, not the MasterPage...

 

[bryanp10]

One of the major misconceptions with MasterPages is that they are somehow
the ASP.NET 2 equivalent of framesets - they aren't at all...

MasterPages are nothing more than UserControls...

When you add a MasterPage to a content page, you are just adding a
UserControl - the content page is the "main" page, not the MasterPage...

--http://www.markrae.net

So maybe a better question is... why the heck did Microsoft implement
MasterPages like this?

 

[Mark Rae]

So maybe a better question is... why the heck did Microsoft implement
MasterPages like this?

As an easy way to provide a uniform structure to pages within the same site.

 

[bruce barker]

if you want it on every page, then use the web.config controls section.

-- bruce (sqlwork.com)

 

[Guest]

You can always register you controls within web.config - this way they will
appear registered on every page within your site. As Mark said master pages
serve different purpose..