Is there a way to keep ASP.Net from mangling control IDs?

Question

5.00/5 (1 vote)

See more:

I have a control:

XML

<asp:TextBox ID="ControlName" runat="server" />

I want to reference it in some Javascript.

ASP.Net mangles the ID into ctl00_ContentPlaceHolder1_ControlName.
To keep things simple I want to refer to it as ControlName in my script: future versions of the page might have the control in a different container which would alter the ID, and I would rather not have to remember to rewrite the script.

Is there any way to instruct ASP.Net, either for this specific control or generally, NOT to mangle the ID?

Posted 23-Mar-11 5:54am

Gregory Gadow

Updated 23-Mar-11 6:17am

Dalek Dave

v2

Add a Solution

Comments

Dalek Dave 23-Mar-11 12:17pm

Edited for Readability.

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)

#realJSOP · Accepted Answer · 2011-03-23T05:57:00

Solution 1

It's happening because you're using a master page. Check this:

http://weblogs.asp.net/scottgu/archive/2006/04/18/Great-New-Advanced-Article-on-ASP.NET-2.0-Master-Pages.aspx[^]

Posted 23-Mar-11 5:57am

#realJSOP

Comments

Gregory Gadow 23-Mar-11 12:07pm

That's what I was afraid of. It makes sense to generate a guaranteed unique id when merging pages, but it's a (redacted) nuisance. Unfortunately, none of the solutions mentioned in your link offer anything I can implement. Thanks for the info.

Dalek Dave 23-Mar-11 12:17pm

Good link John.