Last post Jul 10, 2008 11:48 AM by robertjcallen
Jan 09, 2007 10:58 AM|mkamoski|LINK
ASP.NET Development Team --
Please. I have been waiting for this forever.
Please refactor the VS.NET web page Designer to allow the developer to select items in an <asp:table> tag.
The Designer is great. However, once one puts an <asp:table> tag on the page, everything inside the <asp:table> becomes inaccessible to the Designer.
There is no good reason why this should be the case. The <asp:table> tag is a built-in tag. As such, ASP.NET and the Designer and VS.NET should know everything about it, both at design-time and at run-time. The <asp:table> tag should be well-understood,
parseable, clear, and completlely flexible. It should, therefore, be "designable" to the maximum possible extent. It is simply hard to believe that the <table> tag is more flexible in the Designer than the <asp:table> tag; that seems like backwards-world,
Sidebar -- Why use an <asp:table> tag? Well, because the <asp:table> tag is much more flexible, study, consistent, and clear than a simple <table> tag. Furthermore, <asp:table> is part of ASP.NET itself; therefore, its very existence should be sufficient
to justify its use. That is, if it should not be used, then why does it exist? One is right to assume that the <asp:table> tag must have been created in order to be used. Reasonable people acting prudently would expect as much. Therefore, since the <asp:table>
tag does exist, then it should be fully-functional, at least as much as the lowly <table> tag.
And so on.
Kind people, please consider my humble request. Hear the plight of your people. Come to our aid in this hour of need. We beg your gracious support.
-- Mark Kamoski
Mar 23, 2007 11:03 AM|Eamon|LINK
I cannot express just how much I agree. I signed up just to second this post!!
I refuse to believe we are the only ones that regularly make use of the <asp:Table> object. Not being able to set the properties of any object within an <asp:Table> is a major let down, and although you can work around it by creating all your objects outside
the table, setting their properties and then manually copying the mark-up into the table....this is time consuming and should not be necessary.
If there is some compelling technical reason behind this behaviour, I'd love to hear about it. It would make it easier to accept if I knew why.
Jan 14, 2008 10:57 AM|bmchan|LINK
It's been almost a year, and the new VS 2008 has been released... and we still can't select within an <asp:Table> tag. Kind of annoying to have to move a control out of the table in order to visually work with it.
Jan 19, 2008 01:06 PM|mkamoski|LINK
<<< Useless post deleted by author. >>>
Feb 28, 2008 10:10 AM|cor2879|LINK
Jul 10, 2008 11:48 AM|robertjcallen|LINK
I also agree that is seems silly that the asp:table tag cannot be used with the designer. In short....what good is it in the first place if we cant use the elements/objects within it?
Is there a page/site out there that shows the proper use of the asp:table tag over the standard table tags? Is there some benefit to the asp:table tag other than the fact that it's more verbose that the traditional tr/th/td tags?
I can see the big advantage being that you can setup the table only, then build the table programatically. i.e.: