Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to fix ASP.NET error "The file 'nnn.aspx' has not been pre-compiled, and cannot be requested."?
    primarykey
    data
    text
    <p>I have a VS 2005 web site that I publish using "Publish Web Site", and I clear all the three checkboxes. I also have a deployment project that picks up the published files and creates an MSI. I then install the package on a separate test server.</p> <p>In other words, the whole site is pre-compiled. However, when I go to any .aspx file in a specific subfolder named "Services", I get an HttpException:</p> <blockquote> <p>System.Web.HttpException: The file '/myapp/Services/mypage.aspx' has not been pre-compiled, and cannot be requested.</p> </blockquote> <p>If I go to an .aspx file in an other folder, be it the root or other subfolder, it works properly.</p> <p>The contents of mypage.aspx itself is: <code>&lt;%@ Page Language="C#" AutoEventWireup="true" CodeFile="mypage.aspx.cs" Inherits="Services_mypage" %&gt;"</code></p> <p>In the <code>/myapp/bin</code> folder I can see a <code>mypage.aspx.989dc2fb.compiled</code> file. The content of this seems to point to a certain assembly that is also present in the bin folder.</p> <p>Why is this error occurring? The .compiled file is there, and the assembly is there, and the type in question is present in that assembly (I can see it in Object Browser). Is it something about the name or the content of the .compiled file? Do I have the wrong version somehow? What does the seemingly random number in the .compiled filename mean and is it important?</p> <p>I also want to mention that this issue appeared suddenly, and I'm not sure what changes there can have been done since it worked properly a few days ago (but to the best of my knowledge, none).</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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