Ruslan's Blog : ASPNET

10 URL Rewriting Tips and Tricks

RuslanY Blog — Wed, 08 Apr 2009 22:34:21 GMT

This post describes some of the tips and tricks that one may find useful when solving URL-based problems for their web server or web site. Each tip/trick has a description of a problem and then an example of how it can be solved with IIS 7 URL Rewrite Module . 1. Add or Remove Trailing Slash Many web applications use “virtual URLs” - that is the URLs that do not directly map to the file and directory layout on web server’s file system. An example of such application may be an ASP.NET MVC application with URL format similar to this: http://stackoverflow.com/questions/60857/modrewrite-equivalent-for-iis-7-0 ) or a PHP application with URL format that looks like this: http://ruslany.net/2008/11/url-rewrite-module-release-to-web/ ) If you try to...(read more)

Setup IIS on Server Core – Windows Server 2008 R2

RuslanY Blog — Fri, 27 Feb 2009 01:20:24 GMT

With the addition of .NET Framework to Server Core in Windows Server 2008 R2 the Server Core installation option became even more appealing for those who want to use a very low footprint server for hosting their applications. Availability of .NET framework provides the following great benefits: ASP.NET support – you can now use Server Core to host your ASP.NET applications. IIS Remote Management – Server Core does not provide any user interface other than command line. But if you prefer to use IIS Manager UI to administer IIS, you can now use IIS Remote Manager to connect to IIS on Server Core and perform all the management tasks from within familiar UI of IIS Manager. PowerShell – Windows Server 2008 R2 includes IIS PowerShell snapin, which...(read more)

ASP.NET postbacks and URL rewriting

RuslanY Blog — Thu, 23 Oct 2008 05:04:11 GMT

ASP.NET Web Forms extensively use postback mechanism in order to maintain the state of the server-side controls on the web page. This makes it somewhat tricky to perform URL rewriting for ASP.NET pages. When a server side form control is added to the web page, ASP.NET will render the response with HTML <form> tag that contains an action attribute pointing back to the page where the form control is. This means that if URL rewriting was used for that page, the action attribute will point back to the rewritten URL, not to the URL that was requested from the browser. This will cause the browser to show rewritten URL any time a postback occurs. Let me demonstrate this on an example. Assume you have a very simple web form in a file called default...(read more)

Wildcard script mapping and IIS 7 integrated pipeline

RuslanY Blog — Wed, 01 Oct 2008 03:30:18 GMT

The big benefit of IIS 7 integrated request processing pipeline is the fact that all the nice and useful ASP.NET features can be used for any type of content on your web site; not just for ASP.NET-specific content. For example, ASP.NET SQL-based membership can be used to protect static files and folders. Also, ASP.NET extensibility API’s, such as IHttpHandler and IHttpModule can be used to add custom modules and handlers that would be executed even for non-ASP.NET content. IIS 6 did not have this level of integration. ASP.NET was plugged into IIS 6 as an ISAPI extension and by default was configured to handle ONLY requests mapped to that extension - for example any request that ended with “.aspx” would be be processed by ASP...(read more)