Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Nov 30, 2012 04:43 AM by Diomedes
Nov 28, 2012 10:51 PM|LINK
I started to work on a running project, a web application, where they have just one page, the Default.aspx which loads ascx pages into it, which in turn call other ascx pages into it.
So a simple page is really a composed of at least 15 pages, vb files, resources files, etc, etc.
I find it somewhat over complicated and bloated.
The question is, Is this a normal practice?
Nov 28, 2012 11:09 PM|LINK
Check this out
Nov 29, 2012 01:46 AM|LINK
2005 was a long time ago.
I use webservices when I want to send data to another aplication or get data from something like PayPal, Amazon, etc.
But an entired website?
I guess I still have the same question? How practical you guys think it is and how often is it done?
Nov 30, 2012 03:31 AM|LINK
This way the page will get heavy. I am not sure how much coding are there in each control. If the complete page is full of ascx control. Page size may be huge and also postback operations can be timeconsuming. It it also maintain viewstate imformation for
all the controls in the page which will grow to a huge value. The size of the page is fully dependent on the type of controls are there in the asxc controls. If you need a one page site , its good to make the site completely ajax driven using divs where each
div will maintain each page in it and showing and hiding the divs.
Nov 30, 2012 04:43 AM|LINK
Some pages have 6K lines of code. On my LOCAL server, pages can take from 15 to 30 seconds to load, and the database just has a few records. I can't image how it will run live, on the internet when it get a few thousand records on the tables. >_<
And you are correct, I check the viewstate its BEYOND HUGE.