Tom Christian's Blog : ASP.NET Tip

ASP.NET Tips: Careful Use of Static's

ASP.NET Debugging : IIS — Thu, 18 Sep 2008 10:00:23 GMT

Not sure how many people realize it, but when you start dealing with multiple users access a system (in this case a web server), you have to be very careful what you store in static's (global variables). This is because all the users will have access...(read more)

Improving Time-Critical Code written in C

ASP.NET Debugging : IIS — Tue, 02 Sep 2008 10:00:33 GMT

Writing web pages is very similar to writing any other type of code. You have to understand how it is going to be used and where you need to really make things run as quickly as possible. There are a number of tips on this blog already that deal...(read more)

ASP.NET Tip: Keep hidden files hidden

ASP.NET Debugging : IIS — Tue, 26 Aug 2008 10:00:00 GMT

I have seen a few cases of this so I wanted to let everyone know. If you install the FrontPage Server Extensions (FPSE) on a web server, it will install some configuration files in a directory under your web site called _vti_cnf. This folder...(read more)

ASP.NET Tip: ASP.NET MSDN Site

ASP.NET Debugging : IIS — Wed, 20 Aug 2008 10:00:00 GMT

Have you checked out the MSDN site for ASP.NET lately? It is full of useful information. You can find it at the ASP.NET Developer Center . My favorite things to check out are the “How Do I” videos. They can be really helpful and...(read more)

ASP.NET Tips: Loading a DLL out of the bin directory

ASP.NET Debugging : IIS — Mon, 21 Jul 2008 10:00:00 GMT

Question A customer has created a web project which references a class library project. When deployed to the local machine the web/classes all work fine. When deployed to a ‘shared’ IIS site, the class DLLs exist in the /bin folder, but the...(read more)

ASP.NET and Performance

ASP.NET Debugging : IIS — Mon, 23 Jun 2008 18:29:34 GMT

I wanted to talk about monitoring performance in ASP.NET for a bit. I have already posted a few postings that talk around this issue, namely: ASP.NET Debugging - High Memory part 5 – Fragmentation ASP.NET Debugging - ASP.NET Tips- How to use DebugDiag...(read more)

ASP.NET Tips: What to gather to troubleshoot

ASP.NET Debugging : IIS — Wed, 21 May 2008 15:38:59 GMT

So now that I am done with all the individual posts, I thought I would wrap them all together. So here are all of the posts that I created on gathering information when you are having a problem. Please keep in mind that these are geared towards...(read more)

ASP.NET Tips: What to gather to troubleshoot - part 6 - Recycle due to memoryLimit

ASP.NET Debugging : IIS — Tue, 20 May 2008 16:03:04 GMT

Here is another situation that you may come across and what to do in order to gather information about it. The following steps will configure DebugDiag to automatically capture a memory dump of the ASPNET_WP.exe process recycling when it exceeds the memoryLimit...(read more)

ASP.NET Tips: What to gather to troubleshoot - part 5 - OutOfMemoryException

ASP.NET Debugging : IIS — Mon, 19 May 2008 14:49:41 GMT

So we already talked about what to gather when you are experiencing high memory . But what if you are actually getting a System.OutOfMemoryException? Here is how you capture a dump at the time you are running out of memory. The following steps...(read more)

ASP.NET Tips: What to gather to troubleshoot - part 4 - Deadlocks

ASP.NET Debugging : IIS — Wed, 14 May 2008 15:35:09 GMT

There are two ways to gather data in a Deadlock situation. If you are using Windows 2003 or later (IIS 6.0 or later), then follow the steps in the KB 828222 If you are using an older version of IIS, then follow the steps below: Before the issue...(read more)

ASP.NET Tips: What to gather to troubleshoot – part 3 – Crash

ASP.NET Debugging : IIS — Tue, 06 May 2008 15:39:51 GMT

Defining an IIS Crash A Crash in IIS occurs when an IIS process (INETINFO.EXE, DLLHOST.EXE, W3WP.EXE) terminates unexpectedly. A Crash typically happens when there is an Unhandled Exception caused by an Access Violation, Stack Overflow, etc. In these...(read more)

ASP.NET Tips: What to gather to troubleshoot – part 2 – High Memory

ASP.NET Debugging : IIS — Mon, 05 May 2008 13:28:54 GMT

Identifying a Memory leak A Memory Leak in an IIS process (INETINFO.EXE, DLLHOST.EXE, W3WP.EXE) occurs when Memory Usage in Task Manager continues to consume more than 50% of the physical RAM until running out of system memory or until the process stops...(read more)

ASP.NET Tips: Looking at the finalization queue

ASP.NET Debugging : IIS — Mon, 28 Apr 2008 16:12:48 GMT

So in a previous post, we talked about Understanding when to use a Finalizer in your .NET class so now lets take a look at what the Finalize queue looks like and how to tell if things are bad. The command we use is !finalizequeue in sos: 0:010> !finalizequeue...(read more)

ASP.NET Tips: How to use DebugDiag to track down where a performance problem is coming from

ASP.NET Debugging : IIS — Fri, 25 Apr 2008 19:54:00 GMT

We recently had a case where the customer was having performance problems. They were seeing requests take a few minutes to return and didn’t know what was happening. So they took some dumps while the problem was happening. So we ran this dump through...(read more)

ASP.NET Tips: How to identify a COM call that is blocking GC, causing a memory leak

ASP.NET Debugging : IIS — Tue, 22 Apr 2008 14:42:01 GMT

Problem Description So this is a customer situation we found were the customer was getting an System.OutOfMemoryException. We were able to reproduce this with a console application that just ran: For Iterator = 0 To 99999999999 Regex.IsMatch(CONNECTION_STRING...(read more)