I am trying to load an ASPX URL, but it fails. Well, it loads when I try from IIS Express with the source code, but after I publish it to IIS, it fails with 404.
The file is right there where it should be, it just cannot be downloaded. I turn on Failed Request Tracing, hopefully it will show something. It does: 388 log entries for a single HTTP request. Fortunately the Request Summary view highlights the only warning:
MODULE_SET_RESPONSE_ERROR_STATUS
ModuleName: ManagedPipelineHandler
Notification: EXECUTE_REQUEST_HANDLER
HttpStatus: 404
HttpReason: Not Found
HttpSubStatus: 0
ErrorCode: The operation completed successfully. (0x0)
Not a big help, but it shows which module is guilty. Little joy. I look up the entry in the Complete Request Trace and check the previous entries. AspNetParse and AspNetCompile entries. Hmmm, maybe something is wrong with the ASPX file? Probably not, because it runs on IIS Express, and I have it from a NuGet package.
Anyway, I check the source code. The first line looks suspicious: the @Page directive contains a CodeFile attribute. Unusual. I change it to CodeBehind. Compile, publish.
It works.
I learned it. I share it. 