Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Steve's answer is largely accurate, though the behaviour described (assembly generation on file changes) is predicated on the default <strong>CompilationMode=Always</strong>; you can avoid assembly generation all together with <strong>CompilationMode=Never</strong>. As an aside, note that there is also a <a href="http://msdn.microsoft.com/en-us/library/ms366723.aspx" rel="nofollow noreferrer">new attribute available in 3.5</a>, though it relates specifically to top-level changes that would have previously re-started the application (like web.config):</p> <blockquote> <p>By default, when any change is made to a top-level file in a Web site, the whole site is recompiled. Top-level files include the global.asax file and all files in the bin and App_Code folders. It is safest to recompile everything when one of these files changes because other files in the site, such as .aspx and .ascx files, may reference the objects created by code in top-level files.</p> <p>While recompiling everything works fine for most applications, it could cause a very large application to be unavailable for long periods of time even when minor changes have been made to it. If the application is large enough, it could be unavailable for five to ten minutes or more after a change is made.</p> <p>If you want to be able to change top-level files without causing the whole site to be recompiled, you can set the <strong>optimizeCompilations</strong> attribute of the compilation element in the Web.config file to true.</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload