Comments on: Getting rid of the Naming Container in asp.net 2.0 http://www.gljakal.com/blog/2007/09/12/getting-rid-of-the-naming-container-in-aspnet-20/ Fri, 21 Nov 2008 10:10:05 +0000 http://wordpress.org/?v=2.6.3 By: Andy M http://www.gljakal.com/blog/2007/09/12/getting-rid-of-the-naming-container-in-aspnet-20/#comment-10889 Andy M Thu, 20 Mar 2008 14:30:06 +0000 http://gljakal.com/blog/2007/09/12/getting-rid-of-the-naming-container-in-aspnet-20/#comment-10889 I love this approach, although I'm not looking forward to duplicating all of the standard form controls just to circumvent the naming container "feature". My question though, in my simple tests I seem to lose access to the Text property and ViewState on postback when using my TextBox control in a ContentPlaceHolder on a MasterPages page, have you experienced this as well? I love this approach, although I’m not looking forward to duplicating all of the standard form controls just to circumvent the naming container “feature”.

My question though, in my simple tests I seem to lose access to the Text property and ViewState on postback when using my TextBox control in a ContentPlaceHolder on a MasterPages page, have you experienced this as well?

]]> By: glJakaL http://www.gljakal.com/blog/2007/09/12/getting-rid-of-the-naming-container-in-aspnet-20/#comment-5376 glJakaL Thu, 11 Oct 2007 09:59:31 +0000 http://gljakal.com/blog/2007/09/12/getting-rid-of-the-naming-container-in-aspnet-20/#comment-5376 Joshua: When overriding the NamingContainer property, we are removing the parent-child relationship that is used by asp.net to determine the ID of an object. So, if we have these controls on a webform: <ul>[contentplaceholder]<ul>[UserControl]<ul>[TextBox]</ul></ul></ul> Normally, the name of the generated textbox will be "ctl00$ContentPlaceHolder1$UserControl1$TextBox1". If we override the NamingContainer peroperty of the UserControl, we'll get "UserControl1$TextBox1". This is because (from asp.net's point of view) UserControl1 is no more a child of ContentPlaceHolder1, but it's still the parent of TextBox1! So, in brief, yes you have to override all the low-level controls you use (TextBoxes, HiddenFields, DropDownLists...). Joshua: When overriding the NamingContainer property, we are removing the parent-child relationship that is used by asp.net to determine the ID of an object. So, if we have these controls on a webform:

    [contentplaceholder]
    [UserControl]
    [TextBox]

Normally, the name of the generated textbox will be “ctl00$ContentPlaceHolder1$UserControl1$TextBox1″.
If we override the NamingContainer peroperty of the UserControl, we’ll get “UserControl1$TextBox1″. This is because (from asp.net’s point of view) UserControl1 is no more a child of ContentPlaceHolder1, but it’s still the parent of TextBox1!
So, in brief, yes you have to override all the low-level controls you use (TextBoxes, HiddenFields, DropDownLists…).

]]> By: Joshua Barker http://www.gljakal.com/blog/2007/09/12/getting-rid-of-the-naming-container-in-aspnet-20/#comment-5375 Joshua Barker Wed, 10 Oct 2007 21:58:00 +0000 http://gljakal.com/blog/2007/09/12/getting-rid-of-the-naming-container-in-aspnet-20/#comment-5375 Does this also override the naming for any controls nested under this control (ie, can I just make this change to the one top-level parent control, and all child controls will do the same, or do I have to create a new class for every control type on my page? Does this also override the naming for any controls nested under this control (ie, can I just make this change to the one top-level parent control, and all child controls will do the same, or do I have to create a new class for every control type on my page?

]]>