I have been doing almost exclusively Java development in previous years.
I started my new job and got thrown into ASP (VBScript), ASP.NET, IIS…
Debug – attach process
asp uses vbscript and asp.net (.cs) uses .NET
so in debug mode, pick Script or Managed code (v4.0, v4.5) accordingly
I hope no body needs to know about asp because asp is SOOOO old.
I find most success with enabling debugging on server & client side (settings in IIS), and let that do the work, instead of attaching process in Visual Studio
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
is where the cache is, delete that whenever you need to have a fresh state
Err object – reference
You can view description with Err.Description and maybe Err.Number (not always populated)