Speaking of which...

Consider the following scenario: You have an ASP.NET application which intermittently responds sluggishly. As the problem occurs memory usage is about average, as is CPU usage, but still certain pages respond slower and slower. The machine acts just as Read More...

I got the following question in my Getting started with windbg – post and I thought it might be worth posting the replies in a separate article: Hi Johan, about those threads with an ID of XXXX, should they go away after certain amount of idle time like Read More...

Due to the architecture of web services and web applications they can be quite slow to start. For example on my Windows 2003-box the initial localhost-call to a simple “Hello World!”-web service takes approximately 8 seconds, while the next request is Read More...

This morning I found the following in my inbox: I had set my web servers running on IIS 6 to recycle if they hit 700 MB (Maximum used Memory). Can I run a report to know how many times per day or week the W3WP got recycled. Any suggestions please. Thanks Read More...

Introduction This was originally intended to be a post on identifying and troubleshooting Exceptions using windbg. As I started writing I thought I should write a little something about exceptions in general, just to begin the post. That little something Read More...

Have you read http://support.microsoft.com/?kbid=307340 ? If not, I suggest you do so. If you need convincing or simply want to know why this problem occurs I suggest you keep reading. The problem described in the article above can cause your application Read More...

If your application crashes, hangs and deadlocks it will cause/require the application pool to recycle in order to be resolved, but sometimes your application pool inexplicably recycles for no obvious reason. This is usually a configuration issue or due Read More...

What do finalizers and weak references have in common? Well more than you might think actually. Finalizers Finalizers are clean-up code that will be run at the end of an objects life-cycle. You should only release native resources in the finalizer. When Read More...

This is a subject that has been covered before and I have no intention of writing the ultimate post on the subject. Still I think this is something that every good developer should know. Why do I need to know this? My colleagues and I are quite often Read More...

Quite often I am met with the incorrect assumption that out of memory exceptions can be resolved by adding more memory. I can understand why you'd think that, but actually it won't matter at all. Additional RAM may increase performance, but an additional Read More...

Scenario: A quite common scenario when working in the support industry is a call along theese lines: "My application worked just fine, but now that I've upgraded to IE7, IIS6, Vista, etc. it doesn't work any more. This has got to be a bug! This new version Read More...

What do you do when your StateServer is running high on CPU and your application log is filling up with alerts like: Unable to make the session state request to the session state server.
Please ensure that the ASP.NET State service is started and that the client and server ports are the same. If the server is on a remote machine, please ensure that it accepts remote requests by checking the value of HKLM\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters\AllowRemoteConnection. Read More...

Using the WebClient.Upload method for posting large files will eventually leave you stranded with OutOfMemoryExceptions. This is because WebClient.Upload reads the entire file to memory by default. This is great for smaller files, but not so great if you're working with very large files. This post shows you how to build your own uploader and resolve the problem. Read More...