ServerSide

Its been a few months since the release of LeanServer ScaleUP, a high-performance upload engine for ASP.NET and other IIS 7.0 applications on the Windows Server 2008 platform.   One of the things that has been interesting is how many people have trouble with uploads - and how varied their challenges really are. While we initially built ...

Uploads have always historically been a major pain point for web applications, due to poor performance, spotty reliability, and framework-specific limitations. As more and more websites rely on social networking, user generated content, and in general storing data in the cloud, the ability to support reliable and scalable uploads is rapidly ...

The upload support in the Microsoft web platform has come quite a long way since the early days of IIS. Unfortunately, a number of remaining limitations have made it difficult to offer a quality upload experience, especially for high-traffic sites. As more and more websites rely on user generated content, and in general storing data in the ...

When using the IIS 7.0 Integrated pipeline, you gain access to a ton of cool scenarios where IIS and ASP.NET features work together to provide value for your application – regardless of the application content.Most of these features involve using ASP.NET features (e.g.Forms Authentication) to provide their services for non-ASP.NET ...

Knowing when to restart IIS to pick up various types of changes to your application has traditionally been a challenge. IIS and ASP.NET are both stateful software systems, which heavily rely on cached state that is loaded once to provide high performance.  They also recognize the downside of being stateful - having to refresh the state when ...

Since its release, IconHandler has been a pretty popular module (on its own and with the custom DirectoryListingModule).  Today, I am releasing v2.0 of IconHandler, which contains some much-requested functionality and fixes a few issues that people have reported with the original version.(I don’t RTFM, take me to download)Here are the ...

ASP.NET applications in IIS 7.0 Integrated mode requires configuration changes if they define custom modules or handlers. The primary changes involve moving the module and handler configuration from the ASP.NET’s <httpModules> and <httpHandlers> sections to the IIS 7.0 <modules> and <handlers> sections used by the ...

This month, the Enhance Your Apps With the Integrated ASP.NET Pipeline article is finally out in MSDN Magazine.  I just got several copies in the mail (thanks Howard!).****** UPDATE: Scott Hanselman presents the demos from this article at CodeMash 2008 ******To be honest, I am VERY excited about this article.  I’ve been talking and ...

ASP.NET 2.0 applications on IIS 7.0 are hosted using the ASP.NET Integrated mode by default.  This new mode enables a myriad of exciting scenarios including using super-valuable ASP.NET features like Forms Authentication for your entire Web site, and developing new ASP.NET modules to do things like URL rewriting, authorization, logging, and ...

The “Request is not available in this context” exception is one of the more common errors you may receive on when moving ASP.NET applications to Integrated mode on IIS 7.0.  This exception happens in your implementation of the Application_Start method in the global.asax file if you attempt to access the HttpContext of the request ...