I have been searching for info on this to no avail. The context of why i need this is another question I asked here. More specifically, does creating/updating/deleting files in App_Data cause a pool recycle?
Our ASP.NET 2 web application handles exceptions very elegantly. We catch exceptions in Global ASAX in Application_Error. From there we log the exception and we show a friendly message to the user.
Scenario: I’ve an n-Tier enterprise ASP.NET application deployed using Web Deployment Projects. All tiers produce independent assemblies that is consumed by the ASP.NET application.
UPDATE — process to replicate issue:
What exactly is an application pool? What is its purpose?
We have 64-bit Windows server and we need to explicitly enable the 32-bit mode in the Application Pool used by our web site, because the MS Jet Engine Data Provider used to import data from Excel does not run.
What are pros and cons of having dedicated application pools over keeping web applications in one default app pool?
I have a ASP.NET MVC5 Web Application configured to run on .NET Framework version 4.5.1. However, I notice that when I get an application runtime exception of some sort, the version information displayed at the bottom of the yellow server error page says the following:
What is difference between application domain and application pool?
I have an application which is making use of the RSACryptoServiceProvider to decrypt some data using a known private key (stored in a variable).