I am creating a web application based on ASP.NET 2.0 (in C #), which is primarily intended for intranet use, that is, for use within the organization’s local network.
Regarding the user interface, there are two approaches that I need to choose.
Create a one-page web application with many ASP.NET AJAX 1.0 controls (modal pop-ups) to show categorized content that would otherwise go to a separate .aspx page.
Use the traditional approach and create multiple pages.
The 1 page user interface looks and looks very cool. However, I have doubts about its scalability.
I agreed that the application is intended for use on a local network, but since it is a web application, it can potentially be used over the Internet if the client wants to.
Thanks to the 1-page user interface, there are already about 2,600 lines of code on one .aspx page and another 1,600 lines of code in the code (.aspx.cs)
This will grow - no more - 10,000 lines of code (10,000 in .aspx and 10,000 in .aspx.cs). Therefore, I need to know - how much is too much for an ASP.NET page - is there 2600 + 1600 lines of code to enter the Intranet and Internet access? What about 10,000 lines of code? What is a bottle neck? Is this one-page approach acceptable or do I need to return to the traditional multi-page approach?