I'm noticing that what using a MasterPage with a ContentPlaceHolder that the
content page's controls don't render with the exact same name/id as I'm
giving them at design time. This is causing problems with client-side
scripts that I wish to write.
What can I do to ensure that the name I give the control is the name it
winds up rendering with?
Hi Scott,
As for the control name get changed issue you mentioned, it is actually due
to the ASP.NET's NamingContainer which will mangle the actual ID of any sub
controls inside it. ContentPlaceHolder is such a NamingContainer so that it
will mangle the ID of sub controls in it(so as to avoid ID conflicting).
In ASP.NET, you can use the "ClientID" of control to get the identity that
will render at client-side. You can embed it in to your script.
#How-to use ClientIDs in JavaScript without the ugliness
http://blog.jagregory.com/2006/04/12/how-to-use-clientids-in -javascript-with
out-the-ugliness
#ASP.NET Client-Side Script FAQ
http://www.eggheadcafe.com/articles/20041016.asp
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx .
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Reply-To: "Scott M."
>From: "Scott M."
>Subject: ContentPlaceHolder Control Names
>Date: Thu, 31 Jan 2008 21:57:43 -0500
>
>I'm noticing that what using a MasterPage with a ContentPlaceHolder that
the
>content page's controls don't render with the exact same name/id as I'm
>giving them at design time. This is causing problems with client-side
>scripts that I wish to write.
>
>What can I do to ensure that the name I give the control is the name it
>winds up rendering with?
>
>
Thanks Steven. That's just what I was looking for.
-Scott
"Steven Cheng[MSFT]"
news:Vb0zOlJZIHA.4200@TK2MSFTNGHUB02.phx.gbl...
> Hi Scott,
>
> As for the control name get changed issue you mentioned, it is actually
> due
> to the ASP.NET's NamingContainer which will mangle the actual ID of any
> sub
> controls inside it. ContentPlaceHolder is such a NamingContainer so that
> it
> will mangle the ID of sub controls in it(so as to avoid ID conflicting).
>
> In ASP.NET, you can use the "ClientID" of control to get the identity that
> will render at client-side. You can embed it in to your script.
>
> #How-to use ClientIDs in JavaScript without the ugliness
> http://blog.jagregory.com/2006/04/12/how-to-use-clientids-in -javascript-with
> out-the-ugliness
>
> #ASP.NET Client-Side Script FAQ
> http://www.eggheadcafe.com/articles/20041016.asp
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
>
> ==================================================
>
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
> ications.
>
>
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx .
>
> ==================================================
>
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
> --------------------
>>Reply-To: "Scott M."
>>From: "Scott M."
>>Subject: ContentPlaceHolder Control Names
>>Date: Thu, 31 Jan 2008 21:57:43 -0500
>
>>
>>I'm noticing that what using a MasterPage with a ContentPlaceHolder that
> the
>>content page's controls don't render with the exact same name/id as I'm
>>giving them at design time. This is causing problems with client-side
>>scripts that I wish to write.
>>
>>What can I do to ensure that the name I give the control is the name it
>>winds up rendering with?
>>
>>
>