How server side controls are accessible in code behind files in ASP.NET?

Question

0.00/5 (No votes)

See more:

Just curious!

I was wondering, what actually happens so that any control that is defined in .aspx page and having "runat" attribute is accessible in code behind file?

.aspx page:
<asp:Label rundat = "server" ID= "lbl" />

code behind page:
lbl.Text = "This is a label";

If anyone can share some information about what actually is happening here, what makes my label accessible in code behind after adding "runat" attribute?

What I have tried:

I've tried to find details but getting only how to access controls in code behind page not the actual machinism behind this.

Posted 18-Mar-17 5:09am

sunil kumar meena

Updated 20-Mar-17 0:25am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Karthik_Mahalingam · Accepted Answer · 2017-03-20T00:25:00

Quote:
what makes my label accessible in code behind after adding "runat" attribute?

Whenever you do some change in the ASPX page, the designer file will get updated everytime when the runat="server" attribute is added to the control.
Since the designer file is a partial class, the protected members will be accessed in the code behind file.

for example
when you add an asp button to the page

<asp:Button ID="btn" runat="server" />

in the designer file, it will update as

protected global::System.Web.UI.WebControls.Button btn;

and hence the btn object is accessible in the code behind, since code behind and designer file are acting as partial class.

refer:
c# partial class[^]
Partial Classes and Methods (C# Programming Guide)[^]