Given that the only way to unload dynamically compiled assemblies (to recover memory) is to unload the application domain, how does SharePoint rely on VirtualPathProviders, in particular master pages and page layouts, without attacking this limitation?
Restarting may be delayed by various settings, but not completely excluded, when the main pages and page layouts are updated and published frequently, fix it?
(Is the lack of information about this due to the fact that this is a more theoretical limit that is not common for publishing templates? Have you personally noticed the speed of changes on the main pages or layouts causing instability of the application? Should SharePoint come with a warning?)
Any CMS-esque feature that uses dynamic WebForms (including, by default, MVC views) is prone to instability of speed changes, right?
Updating on pages without compilation:
Without page compilation In ASP.NET 2.0, the compilation model has been significantly reorganized and expanded. The preliminary compilation of the site is perhaps the most popular and loudly requested of new features. Another interesting feature is the non-compiled pages. These are special pages that never compile. So what is the ultimate goal of non-compiled pages and what is the difference between them and static HTML pages? To get started, you create a page without compilation by setting the CompilationMode attribute in the @Page directive to Never. When a page is requested without compilation, the page assembly is not saved and is stored on disk. Instead, an instance of the page builder component is cached in memory and used to generate page output for each request. Page Builder is a special componentwhich supports the page parser when creating the page control tree. When compilation is enabled, the control tree is used to get the compiled class. When compilation is disabled, the control tree is used to get markup. Of course, classes are necessary if you want to give programmers the ability to bind their own code to a page. Pages without compilation are made of server controls and literals, but do not contain code at all.Pages without compilation are made of server controls and literals, but do not contain code at all.Pages without compilation are made of server controls and literals, but do not contain code at all.
. - . . , , $-. . , SharePoint, , . - .
:
1 -
http://haacked.com/archive/2009/04/22/scripted-db-views.aspx