Question

Around 90% of the pages for our websites have no .Net code embedded in them yet are published as .aspx files. I want these to render as fast as possible so I’m removing as much as I can.

Does the .Net page directive have an impact on performance? I am thinking about two factors; the page speed for each GET and what happens when the file changes. The CMS system re-creates each page daily and I’m wondering if this triggers the ASP.Net compilation process.

Answer 1

The <%@ Page %> directive is not required. Without it, the default values for Language and other stuff will be assumed.

By changing a .aspx file, it’ll be recompiled (it doesn’t recompile the whole app though):

Any changes to a dynamically compiled file will automatically invalidate the file’s cached compiled assembly and trigger recompilation of all affected resources. The next time a request to the code is made, ASP.NET recognizes that the code has changed and recompiles the affected resources of the Web application. This system enables you to quickly develop applications with a minimum of compilation processing overhead. (Note that depending on the change to the resources, the result can range from recompiling a single page to recompiling the whole Web site.)