accessing controls in web forms user control

[arvee]

Is there a way to access controls (and their properties) in a user control?
The Web Form Designer marks controls as 'Protected' which makes them
inaccessable from the host form. If I mark them as Public, I can access
them, but the next time the controls are manipulated in the design mode,
they are converted back to Protected. Is there an obvious/easy way around
this?

Thanks.

[MasterGaurav]

Do you want to use the controls "from outside"?
Why do you need that?

I think there may be better ways to achieve what you want to do.

If you can explain you base problem, it may be better.
--
Cheers,
Gaurav Vaish
http://mastergaurav.blogspot.com
http://mastergaurav.org
-------------------

[Lee]

Hi ;)

How about exposing the controls you're interested in as public properties?

e.g.

protected System.Web.UI.WebControls.TextBox m_editName;

public TextBox Name {
get { return m_editName; }
}

"arvee" <no****@spam.not> wrote in news:otale.221$zb.210@trndny04:

Is there a way to access controls (and their properties) in a user
control? The Web Form Designer marks controls as 'Protected' which
makes them inaccessable from the host form. If I mark them as Public,
I can access them, but the next time the controls are manipulated in
the design mode, they are converted back to Protected. Is there an
obvious/easy way around this?

Thanks.

[MasterGaurav]

Hi Lee,

This is where arvee is having trouble.

The VS.Net designer re-marks them as "protected" everything it is
accessed in DesignMode.

But arvee,

I think it can be made public in the "properties" pane. Right click
the control, select properties and make it "public" through that entry.
You should be able to do it.
--
Cheers,
Gaurav Vaish
http://mastergaurav.blogspot.com
http://mastergaurav.org
------------------

[arvee]

MasterGaurav,

My user control contains several web form server controls such as label
controls. My hope was to add the user control to a web form and
programatically set the .Text property of the labels. For example:

Dim newUserControl as myUserControl = LoadControl("blah.apcx")
newUserControl.lblTitle.Text = "Hello World!"

As the Web Form Designer sets the child controls on the user control as
Protected, the code on the Parent web form is restricted from accessing
them. I suppose its a good object design, but in my case, I'd like to
get easy access to them (yeah, I'm lazy).

I worked around it for now by adding my own Public properties that are
exposed from the parent form. In the Page_Load event of the user
control, I assign the public properties (string type) to the .Text
properties of the label controls.

Seemed like there may be an easier way, but hey, that's why we get paid
the big bucks (ha ha).

[Lee]

I understood that he was trying to change the declaration of the control.

e.g. trying to change
protected TextBox Name
to
public TextBox Name

What I'm proposing is adding a public property which simply delegates to
the control declaration.

I tested this prior to posting, hoping to verify that the designer won't
remark the property (it doesn't) - I also noted that it doesn't remark
the control declaration either (certainly not when changing protected to
public in the code editor - I also tried switching back and forth between
the form view, html view and code view), so I dunno what problem arvee is
having.

"MasterGaurav" <ga**********@gmail.com> wrote in
news:11**********************@g43g2000cwa.googlegr oups.com:

Hi Lee,

This is where arvee is having trouble.

The VS.Net designer re-marks them as "protected" everything it is
accessed in DesignMode.

But arvee,

I think it can be made public in the "properties" pane. Right click
the control, select properties and make it "public" through that entry.
You should be able to do it.
--
Cheers,
Gaurav Vaish
http://mastergaurav.blogspot.com
http://mastergaurav.org
------------------

[MasterGaurav]

Arvee:

I would recommend not providing direct acess to any field. Use
properties. I know you are using your code internally (for consumption
within your code) but still, why make it attack-prone by exposing the
field as public?

--
Cheers,
Gaurav Vaish
http://mastergaurav.blogspot.com
http://mastergaurav.org
---------------------