"Kojikabutosv" <ko**********@gmail.comwrote in message
news:OZ**************@TK2MSFTNGP02.phx.gbl...
[top-posting corrected]
>>Hi everybody, i have a master page and with tree buttons, how configure
the buttons to load pages dinamically in wichone pages.
I appreciate that English isn't your first language, but can you please
confirm what you mean by "wichone pages"...?
That said, it sounds like you're making the classic error of confusing
MasterPages with framesets - they are totally different.
A MasterPage is just a UserControl - when you open a content page, the
MasterPage is reloaded every time just like any other UserControl.
So, to move from one content page to another content page, you just
navigate to it like any other page...
thanks Mark, I am sorry my English, try to explain, in a Master Page he
simulated a toolbar that Master Page he created three new pages that are
inherited from the Master Page, but each button these pages will link
different, how I can program the buttons so that the links are different,
some light to help me.
As I've tried to explain, content pages *ARE NOT* inherited from
MasterPages - it's effectively the other way round. I appreciate that the
term 'MasterPage' is very confusing, but a MasterPage really is just a
UserControl. When a content page loads, it opens its MasterPage (just like
any other UserControl) which it then uses to construct the HTML to be
streamed to the client browser - it does this *every time* it's loaded...
If you have e.g. a content page called MyContentPage.aspx, which uses
MyMasterPage.master as its MasterPage, then you navigate to
MyContentPage.aspx just as you would as if it were a 'normal' page...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net