I have a strange problem with ASP.NET. Several sites on my web server run the exact same application. The application has a page that contains a Tab Container from the Ajax Control Toolkit which in it
It looks like there is a possible memory leak with one of our web applications. w3wp.exe is taking about 1.5gb of RAM and our web services are returning an error saying that it is out of memory.Is the
I\'m using VS2010 Beta 2 and I turned on .NET Framework source stepping, so I had to disable \'Just My Code\'.But now the w3wp.exe process doesn\'t show up in the list of processes I can attach to.I\'
I set up iis to handle .exe with \"asp.net 2.0\"s isapi filter to enable dynamic url replacement. For this I setup the extension in iis and added the following line to web.config. Works fine so far.
I am using VSTS 2008 + .Net 3.5 + C#. And I developed a custom Forms authentication module for IIS 7.0 and I attach to w3wp.exe to debug this module. During the attach process (I just select Tools ->
The ASP.NET web app project I\'m currently working on is getting slower over time to re-load (In IIS or the .NET dev server). Currently it takes:
On a production environment, how can one discover which Asp.Net http requests, whether aspx or asmx or custom, are causing the most memory pressure within a w3wp.exe process?
A simple question: Is the AppPool same as the worker process w3wp? If this is the case when the w3wp.exe shuts down after \"idle timeout\" why does the AppPool show as still running on the IIS Manag
加载中,请稍侯......