Comments on: IDing the Problem of ASP.NET http://www.search-this.com/2008/08/20/iding-the-problem-of-aspnet/ Internet Marketing, Website Promotion and Blogging Advice Sun, 29 Jan 2012 02:18:27 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Tony http://www.search-this.com/2008/08/20/iding-the-problem-of-aspnet/comment-page-1/#comment-88129 Tony Wed, 27 Aug 2008 15:45:29 +0000 http://www.search-this.com/?p=714#comment-88129 Lets try again, within angle brackets: %= contentTop.ClientID % Lets try again, within angle brackets:

%= contentTop.ClientID %

]]> By: Tony http://www.search-this.com/2008/08/20/iding-the-problem-of-aspnet/comment-page-1/#comment-88128 Tony Wed, 27 Aug 2008 15:44:49 +0000 http://www.search-this.com/?p=714#comment-88128 All that white space should have shown: All that white space should have shown:

]]> By: Tony http://www.search-this.com/2008/08/20/iding-the-problem-of-aspnet/comment-page-1/#comment-88127 Tony Wed, 27 Aug 2008 15:43:54 +0000 http://www.search-this.com/?p=714#comment-88127 You can also use: Like so: var cTop = $get(" "); or var cTop = $("#"); The ASP.NET engine will parse the IDs for you at runtime. The bad news is that you cannot use this method in HTML markup such as: <input type="button" onclick="Show(' ')" /> This will parse and render the encoded version of the angle brackets. (&lgt;) You can also use:

Like so:

var cTop = $get(”
“);

or

var cTop = $(“#”);

The ASP.NET engine will parse the IDs for you at runtime. The bad news is that you cannot use this method in HTML markup such as:

<input type=”button” onclick=”Show(‘
‘)” />

This will parse and render the encoded version of the angle brackets. (&lgt;)

]]> By: Golgotha http://www.search-this.com/2008/08/20/iding-the-problem-of-aspnet/comment-page-1/#comment-86281 Golgotha Thu, 21 Aug 2008 13:47:16 +0000 http://www.search-this.com/?p=714#comment-86281 @Adrain and Brian - right, of course asp.net does this with the intention of avoiding duplicates. BUT, we should be able to ID the controls ourselves and then have controls like the GridView, ListView and Repeater do their auto-IDing off of our initial ID. It's very rare that you would try and target a specific row within these server-controls with CSS or JavaScript, but it's very likely that you would want to target the controls in general. Even more likely is targeting asp:Panels, asp:PlaceHolder, asp:Button, asp:DropDownList and all the rest. @Jack - Actually no, I know nothing about MVC. But when I read things like "It enables you to achieve and maintain a clear separation of concerns" and "It provides more control over the URLs you publish in the application and over the HTML that is emitted by the application" I can't help but think I need to start learning it. If it's <em>all that</em> then why doesn't that just get rolled into ASP.NET 4.0? @Adrain and Brian – right, of course asp.net does this with the intention of avoiding duplicates. BUT, we should be able to ID the controls ourselves and then have controls like the GridView, ListView and Repeater do their auto-IDing off of our initial ID.

It’s very rare that you would try and target a specific row within these server-controls with CSS or JavaScript, but it’s very likely that you would want to target the controls in general. Even more likely is targeting asp:Panels, asp:PlaceHolder, asp:Button, asp:DropDownList and all the rest.

@Jack – Actually no, I know nothing about MVC. But when I read things like “It enables you to achieve and maintain a clear separation of concerns” and “It provides more control over the URLs you publish in the application and over the HTML that is emitted by the application” I can’t help but think I need to start learning it. If it’s all that then why doesn’t that just get rolled into ASP.NET 4.0?

]]> By: Brian Nash http://www.search-this.com/2008/08/20/iding-the-problem-of-aspnet/comment-page-1/#comment-86020 Brian Nash Wed, 20 Aug 2008 20:48:21 +0000 http://www.search-this.com/?p=714#comment-86020 Part of the reason asp.net does this is because the controls (like a button or label) can repeat inside a datagrid or repeater. This way they get a unique id. I imagine your way would work fine for a single control on a page. If you register the whole javascript function in C# code you can fill in individual client id's. But that's pretty painful unless you just have a couple of little javascript functions. I always got the feeling that javascript support with asp.net was sort of "fine, if we have too". Part of the reason asp.net does this is because the controls (like a button or label) can repeat inside a datagrid or repeater. This way they get a unique id. I imagine your way would work fine for a single control on a page.

If you register the whole javascript function in C# code you can fill in individual client id’s. But that’s pretty painful unless you just have a couple of little javascript functions.

I always got the feeling that javascript support with asp.net was sort of “fine, if we have too”.

]]> By: Adrian Banks http://www.search-this.com/2008/08/20/iding-the-problem-of-aspnet/comment-page-1/#comment-85990 Adrian Banks Wed, 20 Aug 2008 19:15:57 +0000 http://www.search-this.com/?p=714#comment-85990 The ids are auto-generated to avoid duplicates. If you have a control inside a repeater control, you'd end up with several controls with the same id. The ids are auto-generated to avoid duplicates. If you have a control inside a repeater control, you’d end up with several controls with the same id.

]]> By: Jack Hughes http://www.search-this.com/2008/08/20/iding-the-problem-of-aspnet/comment-page-1/#comment-85938 Jack Hughes Wed, 20 Aug 2008 16:08:02 +0000 http://www.search-this.com/?p=714#comment-85938 Good hint...had a look at the MVC framework yet for ASP.NET? Good hint…had a look at the MVC framework yet for ASP.NET?

]]>