I’ve just tried to deploy my first web application to IIS on my Windows 7 Home Premium notebook. After creating the application, I had to change to the Classic App Pool, then set that pool for framework 4.0. Now I get the following error:
There are several questions about leveraging browser caching but I didn’t find anything useful for how to do this in an ASP.NET application. Google’s Pagespeed tells this is performance biggest problem.
So far I did this in my web.config:
I don’t know what’s wrong with my machine, but it’s a while that I’m getting the following strange error from ASP.NET (for all my applications).
I have an ASP.NET app which needs to save files to a network share (Samba).
On IIS 6, what does an IIS reset do?
I have various servers (dev, 2 x test, 2 x prod) running the same asp.net site.
I have an ASP.NET Core app that runs great in IIS Express. Similarly, if I launch the app from the command line via dotnet run, everything works smoothly:
I have web-site that uses MS Excel files read/write.
Background story:
I typically use URL rewriting to pass content IDs to my website, so this