dpanattoni
IS-IT--Management
I know this sounds basic, but I'm not fully understanding some principle concepts here.
Why, when designing an aspx page from within Visual Studio's design page, does it create a <TABLE> tag outside of the form, a <TABLE> tag inside of the form, and then within the 2nd table, it creates my control object, such as a button?
If this is normal, how do I control it? I have designed a page several times that looks proper on the design screen, but when I run it, it looks nothing like what I've designed due to the fact that the HTML code has put everything in multiple tables. I have been fixing this by editing the HTML code to get rid of the tables, but as soon as a new save is made on the design page, all is lost and I have to start again.
I can't imagine that most programmers are ignoring the design page and just writing straight HTML. This would be fine for most complex designs, but why have a design page?
Thanks,
DP
Why, when designing an aspx page from within Visual Studio's design page, does it create a <TABLE> tag outside of the form, a <TABLE> tag inside of the form, and then within the 2nd table, it creates my control object, such as a button?
If this is normal, how do I control it? I have designed a page several times that looks proper on the design screen, but when I run it, it looks nothing like what I've designed due to the fact that the HTML code has put everything in multiple tables. I have been fixing this by editing the HTML code to get rid of the tables, but as soon as a new save is made on the design page, all is lost and I have to start again.
I can't imagine that most programmers are ignoring the design page and just writing straight HTML. This would be fine for most complex designs, but why have a design page?
Thanks,
DP
