Address Content Page Controls from Master

[=?Utf-8?B?UmJydA==?=]

There is a lot of good material related to using Master Pages for formatting
controls and putting common design elements on multiple pages.

I have VB.NET code that is common to all of my pages for doing things like
rendering controls, making database connections, instantiating custom
classes, etc...

I am trying to figure out how to put code in the Master Page that will
address controls on the content pages which use that master - say for example
to set the text and tooltip of a button or label.

Is this possible? If so, how?

I tried defining a BasePage class and inheriting from that, but am having
trouble with the declarations for the events in the inheriting page.

Thanks!

[bruce barker]

this is probably a poor design. the master page is just a control on the
actual page.

a better approach is your original approach of a base page. any problems
coding for events you had with a basepage you will have with a master.

you should spend the time to understand delegates, events and overrides
to overcome your original coding errors.

-- bruce (sqlwork.com)
Rbrt wrote:

There is a lot of good material related to using Master Pages for formatting
controls and putting common design elements on multiple pages.

I have VB.NET code that is common to all of my pages for doing things like
rendering controls, making database connections, instantiating custom
classes, etc...

I am trying to figure out how to put code in the Master Page that will
address controls on the content pages which use that master - say for example
to set the text and tooltip of a button or label.

Is this possible? If so, how?

I tried defining a BasePage class and inheriting from that, but am having
trouble with the declarations for the events in the inheriting page.

Thanks!

[Bryan Porter]

I wholeheartedly agree with Bruce, the base page is definitely the way to
go, but if you're looking for a quick fix FindControl will do it.

Mind you, there are caveats, big ones, but it'll get the job (poorly) done.

--
Regards,

Bryan Porter
http://www.bryanporter.com/

"What A Horrible Night To Have A Curse!" - S. Belmont
"bruce barker" <no****@nospam.comwrote in message
news:us**************@TK2MSFTNGP03.phx.gbl...

this is probably a poor design. the master page is just a control on the
actual page.

a better approach is your original approach of a base page. any problems
coding for events you had with a basepage you will have with a master.

you should spend the time to understand delegates, events and overrides to
overcome your original coding errors.

-- bruce (sqlwork.com)
Rbrt wrote:

>There is a lot of good material related to using Master Pages for
formatting controls and putting common design elements on multiple pages.

I have VB.NET code that is common to all of my pages for doing things
like rendering controls, making database connections, instantiating
custom classes, etc...

I am trying to figure out how to put code in the Master Page that will
address controls on the content pages which use that master - say for
example to set the text and tooltip of a button or label.

Is this possible? If so, how?

I tried defining a BasePage class and inheriting from that, but am having
trouble with the declarations for the events in the inheriting page.

Thanks!

[=?Utf-8?B?UmJydA==?=]

Yeah I am trying to do that but for some reason I keep getting a blue
squiggly that talks about using WithEvents when I put a Handles statement in
an Event Handler of the child (inheriting) page.

This used to be simple in 1.1 !

"bruce barker" wrote:

this is probably a poor design. the master page is just a control on the
actual page.

a better approach is your original approach of a base page. any problems
coding for events you had with a basepage you will have with a master.

you should spend the time to understand delegates, events and overrides
to overcome your original coding errors.

-- bruce (sqlwork.com)
Rbrt wrote:

There is a lot of good material related to using Master Pages for formatting
controls and putting common design elements on multiple pages.

I have VB.NET code that is common to all of my pages for doing things like
rendering controls, making database connections, instantiating custom
classes, etc...

I am trying to figure out how to put code in the Master Page that will
address controls on the content pages which use that master - say for example
to set the text and tooltip of a button or label.

Is this possible? If so, how?

I tried defining a BasePage class and inheriting from that, but am having
trouble with the declarations for the events in the inheriting page.

Thanks!

[Scott Roberts]

Gotcha.

Our FormView is far too customized to be useful to anyone else. We've got
all kinds of crap in there. But the part you might be interested in is a
very simple recursive routine that binds controls to our custom business
object. Here it is:

protected virtual void GenerateFieldBindings(Control containerControl)
{
// Loop through all controls and attempt to wire-up fields by matching
// the control ID to the field name.
foreach (Control c in containerControl.Controls)
{
if (c.ID != null)
foreach (IField f in BoundObject.Fields)
if (c.ID.ToUpper() == f.FieldName.ToUpper())
AddFieldBinding(c, f);

GenerateFieldBindings(c);
}
}
So, if you replace "BoundObject.Fields" with
"YourCollectionOfObjectsObtainedFromYourDB" you're pretty much set. Just
pass in a reference to your "page" to get the ball rolling (e.g. in the
Page_Load just call GenerateFieldBindings(this)).

"Rbrt" <Rb**@discussions.microsoft.comwrote in message
news:E6**********************************@microsof t.com...

>I am building an application that is multilingual. The text elements are
stored in a database table and when the page loads, I get all the text
stuff
for the controls on that page (text, tooltip, messages for validators,
etc...) in the current user's language and then I go through each control
and
set the text property, tooltip property, what have you. To do this I have
created a special interface class that does the heavy lifting - reading
the
database, getting the properties, etc...

I'd be interested to hear more about that custom FormView if you've the
time.

[=?Utf-8?B?UmJydA==?=]

Thank you!

"Scott Roberts" wrote:

Gotcha.

Our FormView is far too customized to be useful to anyone else. We've got
all kinds of crap in there. But the part you might be interested in is a
very simple recursive routine that binds controls to our custom business
object. Here it is:

protected virtual void GenerateFieldBindings(Control containerControl)
{
// Loop through all controls and attempt to wire-up fields by matching
// the control ID to the field name.
foreach (Control c in containerControl.Controls)
{
if (c.ID != null)
foreach (IField f in BoundObject.Fields)
if (c.ID.ToUpper() == f.FieldName.ToUpper())
AddFieldBinding(c, f);

GenerateFieldBindings(c);
}
}
So, if you replace "BoundObject.Fields" with
"YourCollectionOfObjectsObtainedFromYourDB" you're pretty much set. Just
pass in a reference to your "page" to get the ball rolling (e.g. in the
Page_Load just call GenerateFieldBindings(this)).

"Rbrt" <Rb**@discussions.microsoft.comwrote in message
news:E6**********************************@microsof t.com...

I am building an application that is multilingual. The text elements are
stored in a database table and when the page loads, I get all the text
stuff
for the controls on that page (text, tooltip, messages for validators,
etc...) in the current user's language and then I go through each control
and
set the text property, tooltip property, what have you. To do this I have
created a special interface class that does the heavy lifting - reading
the
database, getting the properties, etc...

I'd be interested to hear more about that custom FormView if you've the
time.