I suppose it just offends my sense of decency to put inline VBScript on an .aspx page. So, I started looking at the jQuery selector core and found a nice little gem. Now, it's not perfect, and there are certainly ways for it to fail, but in general I've found that if you feed the following the proper context, it always works:
The great part about this from my point of view is that my jQuery markup will match my .net markup. This leads to the ability to loop through jQuery objects and do a bunch of things without needing to first determine the .net rendered client ID. Also, I can use .net runat=server objects with jQuery and they will work together. In other words, if I want to take some fields in an asp:Panel and paint them pretty or use JSON to complete them, I can do that with jQuery. But if I want to then take the values of those fields and do server-side work with them when a button is clicked, the value of those fields will be available in my .vb file as part of the page controls.
If you are concerned about controls with ID's that match across multiple parts of you page, you could narrow the scope of the selector like this:
This works based on jQuery's selector model $([object],[object context]). That object context part is optional and many times not necessary, but if you want jQuery to stick to one section of your document, this is a handy way to do it...and we can use the .net Panel object because we are referring to it with the id$=MyPanel1 trick.