Yes, I agree with you regarding those elements which are dynamically
renamed, they should be avoided. I have read somehwere that you should be
able to override the UniqueID property. Thats one possibly for tomorrow to
look at as its late here.
Perhaps I am missing the point with .net, but its seems that although we
have these wonderfull new schemes, it would sometimes appear that those who
design them dont have real world development experience.
Im sure this isnt true, but it feels that way sometimes.
Another example is the new naming convention which is like
myInstanceNameTextBox instead of txtTextBox. Well, I dont know about anyone
else, but to me this is a crazy way of doing it. When I type me. or this.
using prefixes I then get the ability to list all the available controls by
type ( which usually represent the majority of the members of the form
class. Now all the wizards use the new convention.
Im sure somone has a rational, but I dont know what it is. So far, I really
havent found that much in 2005 which I can trully say has made my life that
much easier. In fact its the opposite, the new controls dont really fit into
a DLL like before.
"Mark Rae" <ma**@markNOSPAMrae.netwrote in message
news:%2******************@TK2MSFTNGP02.phx.gbl...
"Just Me" <news.microsoft.comwrote in message
news:uv**************@TK2MSFTNGP05.phx.gbl...
>OK, thanks for that, yes that is exactly what I am referring to. The
reason im asking is that I want to make the css clear what I am referring
to by prefixing the selector with the form ID
#formname .className #id etc etc
I guess I can set this by coding it, but it seems a little odd that you
cant do it at design time.
I totally agree with you! There are some parts of ASP.NET that are totally
unfathomable to me, and this is one of them... :-)
I've never been able to get a satisfactory explanation as to why forcing
the ID of a MasterPage's <asp:Formtag to 'aspnetForm' is a "good
idea"...
However, what is definitely a "bad idea" is hard-coding DOM element names
into your CSS, especially with MasterPages (and other UserControls),
because of the way they are renamed dynamically at render-time...
