Last post Jul 27, 2020 08:22 AM by Sean Fang
Jul 19, 2020 07:27 PM|fazioliamboina|LINK
its strange to me that i cant find anyone else having this same problem on google, however:
Organising .aspx pages into subfolders on webforms seemed to somehow run all folders in different processes causing freezes when navigating between folders while doing href's at runtime.
So if i load a page in folder "/Register/Index.aspx", then the server is showing signs of booting up something. and once completed, all pages inside that folder seem to work normally again, until i navigate to a page in another folder like "/Login/LostMyPassword.aspx"
and then it is somehow showing some kind of boot-up freeze all over again.
so its like all subfolders in a webforms project are running independendly, but still share the same application cashe.
Jul 19, 2020 08:02 PM|mgebhard|LINK
There are two types of Web Forms projects; Web Application and Web Sites. Web Applications compile all the code behind pages into a DLL. Web Sites are compiled on demand where each file is an assembly.
I assume you built a Web Site project and are describing the time it take to compile on demand. If your application is locking up and requires a restart then there is a problem with your code.
Jul 19, 2020 11:14 PM|fazioliamboina|LINK
i know that. i use the web application project. it compiles before i publish it to the server.
the problem i have is not code related. All individual folders have an individual startup time.
you can create your own empty project, add some folders, and some empty pages into them. and start debugging. you will see that the website hangs óne time for each folder you navigate to. after a folder is loaded, all subpages respond normally again. This
is default behavior.
i want the application to boot up all folders in 1 time. my users are experiencing it as lag when changing between folders, because my interface is very graphical. so it feels like an App, and when a folder needs to load in, the user has forgotten that its
a website and they start to click the mouse everywhere because they panic.
Jul 27, 2020 08:22 AM|Sean Fang|LINK
By default, ASP.NET Web pages and code files are compiled dynamically when users first request a resource such as a page from the Web site. After pages and code files have been compiled the first time, the compiled resources are cached, so that subsequent
requests to the same page are extremely efficient.
Moreover, ASP.NET can also precompile an entire site before it is made available to users, which brings below advantages:
Faster response time for users, since pages and code files do not have to be compiled the first time they are requested. This is particularly useful on large sites that are updated frequently.
A means to identify compile-time bugs before users see a site.
The ability to create a compiled version of the site that can be deployed to a production server without source code.
However, Precompiling a Web site compiles only that site, not any child sites.
If a Web site contains a child folder that is marked as an application in IIS, the child application is not compiled when you precompile the parent folder.
Therefore, I am afraid that you could not boot up all folders in one times.