Why are blank pages being served with “200 OK” for asp.net errors in IIS 8.5 (Win 2012 R2)?
I’ve set up a new Windows 2012 R2 server running IIS 8.5.
iis
Server.MapPath to go two folder back from root
Here is how I do it:
ASP.NET Core 404 Error on IIS 10
I have a problem with ASP.NET Core web application running on IIS 10.
I am developing a Single Page Application with AngularJS.
Visual Studio 2012: Unable to attach the process. A debugger is already attached
I built solution, created application in IIS and mapped it to the application folder. It works fine. Then I go to “Attach to Process”, there are two w3wp.exe processes in list, but for one of them I get error “Unable to attach the process. A debugger is already attach.” I’ve googled it but I can’t find solution for my problem.
IIS 7.5 Application Initialization for ASP.NET web service (warmup) without remapping requests
I’m trying to use the IIS 7.5 Application Initialization extension to configure a warmup process for my web application. This is an approach I am taking to minimize slow downs caused by application pool recycling, which is a problem explained well in other questions on Stack Overflow.
ASP.NET Core application debugging without publishing on IIS
I used to use asp.net mvc4 and in IIS my website’s physical path would point my solution directory, and every time I update my code, I just re-build my solution and then I can use “Attach to process” (w3wp) to start debugging.
Is there an equivalent to the mod_pagespeed Apache module for IIS?
Is there an equivalent to mod_pagespeed Apache module but for IIS?
.axd files generate a 404 error
Why do all of my .axd files generate a 404 error when on our production server?
Bad Request – Invalid Hostname ASP.net Visual Studio 2015
After debugging my website in Visual Studio 2015, I can visit it via localhost:50544. I would like to visit my website on a different computer from which it is being served upon that is also on the same network. To do this I should be able to visit that computers address which is 192.168.1.13:50544.
ASP.NET MVC thinks my virtual directory is a controller
I have a virtual directory under my MVC website in IIS called “Files”. This directory is at the same level as my Views directory. When I link to a file from my MVC app to a file under my Files directory, I get the following error: