Comments by ryanconrad (Top 1 by date)

Reason for my vote of 1 \n Your content type is incorrect. ContentType is not the file extension, it should be something like "image/png" or "image/jpeg".

You are also claiming that this can help application performance. This is not a true statement. Images are normally delivered as static files, not having to be processed by ASPNET, by running all images through this, it is actually putting a heavier load on the server. Also, the browser will not cache the images very well because they will all have the same url.

You are also using double the memory to load your image, mainly because of the issue with saving a png directly to the output stream, but still using double. The original image is read from disk and loaded in memory. then you create another image to hold the resized image.

I would not run this in a production environment. It would actually degrade the performance of the entire application. You are better off creating your images sized to how you need them ahead of time and let them load as static files.