I've been using IIS 7 on Vista to develop an ASP.NET application, and have noticed some inconsistent behaviour between Integrated and Classic application pool pipeline modes. Using Fiddler, I observed the following lines of code were not producing the
GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist? When all my processign is done i set everything to null and then: GC.Collect();
Hello. I just discovered this method and tried it out. It seems that the CodeFile (.aspx.vb) is not considered a dependency; yet, if I chose to have that same code in the .aspx page, altering it would change the Last-Modified value.