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
In case of a update and then recompile. copy all the files from bin folder again and also the particular file updated from its respective folder.
In my case 'nnn.aspx.xxxxxxxx.compiled' file was removed by WebDeploy, because I ran 2 simultaneous jobs in the same Jenkins workspace. The second job removed some files during WebDeploy package creation.
This is the solution for VS 2008.
Please tick the box as shown below to resolve the issue.
Just as a footnote to all of the above answers that resolved the issue via republishing to replace a missing assembly... While i have solved this issue previously with that same solution, i have just encountered another reason for it's occurrence which may assist others.
The AppPool that my site was running under had it's "Enable 32-bit applications" setting set to false. By changing this to true via the "Advanced Settings" dialog of the app pool i resolved my issue.
Hope that helps some other poor sucker.
This error can also occur if you have a .compiled file in bin for a page that is no longer a part of your project. You receive this in place of 404 essentially. Remove the .compiled file and then you get 404.
I ran into the same issue. My problem was fixed by deleting the files in the temporary asp.net files folder in this folder:
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root