Managing IIS6 Web Server
What:MSDN Webcast: Knee-Jerk Reactions to Proactive Solutions: Improved SharePoint PerformanceAttend this webcast to learn one dozen easy-to-implement performance tips for Microsoft Office SharePoint Server 2007. We discuss a wide range of topics from adjusting out-of-the-box settings to identifying memory leaks in custom code. We also describe several ways to proactively improve the user experience and squeeze more performance out of a SharePoint Server farm. Anyone currently designing a SharePoint Server implementation can benefit from this webcast.When:Friday, July 10, 2009 12:00 PMWhere:MSDN Web Cast Live Meeting Technorati Tags: Presentation,SharePoint Performance,MSDN Web Cast,ASP.NET MVP
How to Enable IIS 6.0 Compression for SharePoint: Microsoft’s Internet Information Server (IIS) has long support HTTP Compression. However, supporting and implementing compression are two different things. Many settings within IIS are easily configured from the IIS Admin GUI. Unfortunately, enabling and configuring compression is not supported through the GUI and requires editing the IIS Metabase. THe metabase can be edited manually or updated from a command prompt. The commands can be combine into the following script: Script: cd c:\inetpub\adminscripts REM Turn On Compression cscript adsutil.vbs set w3svc/filters/compression/parameters/HcDoDynamicCompression true ...
Last year we deployed a new underwriting system. Since the Fall of 2006 we have been steadily releasing updates to the system. Supporting the large user-base of this application has required us to improve our debugging and performance monitor skills. For example, we have become huge fans of unit testing and made strides to better understand memory management and profiling. To protect the health of the application we needed to understand the recycling of application pools / worker processes.
Thoughts on Application Pool Recycling and Application Availability explains in detail how IIS6 is designed to gracefully transfer client connections to...
I ran into an issue where cetain images served from a virtual directory, mapped to Network Attached Storage (NAS) via a UNC path would not display. After quite a bit of detective work I noticed that the images failing to display where those of about 600KB in size.
Most .NET Web Applications are built using .ASPX and ASCX (User Controls) Files. However, ASP.NET provides an easy way to build HTTP Handlers via .ASHX Files. You might want to use HTTP Handlers when the output of your application isn't going to a web browser.