Comments on: ASP.NET 2.0 name mangling http://uzair.nairang.org/articles/2005/10/14/asp-net-2-0-name-mangling/ Where Uzairs Roam Thu, 20 Nov 2008 10:08:16 +0000 http://wordpress.org/?v=2.6.2 By: jrush http://uzair.nairang.org/articles/2005/10/14/asp-net-2-0-name-mangling/#comment-15504 jrush Mon, 02 Jul 2007 22:09:12 +0000 #comment-15504 <p>Sorry that didn't convert over :</p> <p>var menuID = "<%=MainMenu.ClientID%>_tblMenuBar";</p> Sorry that didn’t convert over :

var menuID = “<%=MainMenu.ClientID%>_tblMenuBar”;

]]> By: jrush http://uzair.nairang.org/articles/2005/10/14/asp-net-2-0-name-mangling/#comment-15503 jrush Mon, 02 Jul 2007 22:06:17 +0000 #comment-15503 <p>Well I just set this in my JS like so:</p> <pre><code>_tblMenuBar"; // --&gt; </code></pre> <p>But I've been very pissed off that MS did this. It would have taken very little effort to track the element IDs a diff way. Not only have they made it difficult to use getElementById (a staple in JS), but they hosed us when using #elementID in CSS. What were they thinking? Obviously they didn't. Thanks Microsoft - way to backtrack</p> Well I just set this in my JS like so:

_tblMenuBar";
// --&gt;

But I’ve been very pissed off that MS did this. It would have taken very little effort to track the element IDs a diff way. Not only have they made it difficult to use getElementById (a staple in JS), but they hosed us when using #elementID in CSS. What were they thinking? Obviously they didn’t. Thanks Microsoft - way to backtrack

]]> By: Joshua Coady http://uzair.nairang.org/articles/2005/10/14/asp-net-2-0-name-mangling/#comment-11659 Joshua Coady Mon, 09 Apr 2007 23:31:46 +0000 #comment-11659 <p>Well, you can put the majority of the logic in a .js and expose it with a function that takes the id as input. Then you could use</p> <p>var mydata = dowork(”<%= MyField.ClientID %>”);</p> <p>But I digress because I dont like to use inline code blocks. Using the new client script manager has an advantage in that you can simple tell it to include the script elements instead of having to include them manually every time in your code.</p> Well, you can put the majority of the logic in a .js and expose it with a function that takes the id as input. Then you could use

var mydata = dowork(”<%= MyField.ClientID %>”);

But I digress because I dont like to use inline code blocks. Using the new client script manager has an advantage in that you can simple tell it to include the script elements instead of having to include them manually every time in your code.

]]> By: Jay Tavares http://uzair.nairang.org/articles/2005/10/14/asp-net-2-0-name-mangling/#comment-1058 Jay Tavares Thu, 28 Sep 2006 14:54:40 +0000 #comment-1058 <p>True... if you use code blocks. Don't try to seperate your javascript into its own file. :o</p> True… if you use code blocks. Don’t try to seperate your javascript into its own file. :o

]]> By: Marc Fearby http://uzair.nairang.org/articles/2005/10/14/asp-net-2-0-name-mangling/#comment-416 Marc Fearby Tue, 19 Sep 2006 10:08:24 +0000 #comment-416 <p>Why go to all the bother of declaring a ClientScriptManager when you could just embed the following inside your own script block within the .aspx itself?</p> <p>var MyField = document.getElementById("<%= MyField.ClientID %>");</p> <p>I'm relatively new to ASP.NET, so I could be missing something here, but ClientScriptManager seems like an oversized sledge-hammer for a very simple job.</p> Why go to all the bother of declaring a ClientScriptManager when you could just embed the following inside your own script block within the .aspx itself?

var MyField = document.getElementById(”<%= MyField.ClientID %>”);

I’m relatively new to ASP.NET, so I could be missing something here, but ClientScriptManager seems like an oversized sledge-hammer for a very simple job.

]]>