May 25 2008

IIS 7.0 Resource Kit Book is published

Category:[email protected] @ 20:05

The Internet Information Services (IIS) 7.0 Resource Kit is now published and you can get it from the following link:

Internet Information Services (IIS) 7.0 Resource Kit


I strongly recommend this book to read to get to know everything you want about IIS 7.0.




May 23 2008

Visual Studio 2008 Hotfixes and SP1 Beta

Category:[email protected] @ 06:21

Before installing VS 2008 SP1 Beta, check if you had installed any previous hot fixes. If yes, then you need to install the Hotfixes Cleanup utility before installing the SP1 beta.

Where to get the cleanup utility? Visual Studio 2008 Hotfix Cleanup Utility for Installing Visual Studio 2008 SP1


Hope this helps,




May 22 2008

Running Classic ASP pages inside Classic Mode in IIS 7.0

Category:[email protected] @ 19:45

I have been trying for a while to run classic ASP pages inside an application hosted on IIS 7.0 and running under the Classic Mode Application Pool.

In IIS 6.0, there was the concept of Wild-Card Mapping where you map all requests to the ASP.NET ISAPI extension to be processed by the ASP.NET engine. As you know, when running an application hosted inside IIS 7.0 and running under the Classic Mode application pool, it behaves similarly as if it was hosted inside IIS 6.0.

To define a wild-card in II 7.0 for applications running under Classic Mode application pool follow the steps:

  1. Click on the application you want to configure the wild-card for it inside IIS 7.0.
  2. Make sure the application is running under the classic mode application pool
  3. On the home page of the application, double click on the Handler Mappings applet. This applet shows all the extension mappings defined for the current application that are already inherited from the Default Web site.
  4. Click on the Add Script Map  on the Actions pane on the right. A dialog box pops up allowing you to enter the details of the mapping you want. The diagram is shown in the figure below.

In the Request Path field you enter "*". In the Executable field you enter the ASP.NET ISAPI extension so that all requests will be redirected to ASP.NET engine. In the Name field you enter the name of the new mapping you are defining.

Once you have defined the above, click on the Request Restrictions button to show the dialog box in the figure below.


Clear the Checkbox above so that you don't put any restrictions on the requests to be mapped to the ISAPI extension defined.

Now when you run the ASP page inside your application, it will work fine! What happens is that the .asp page will first be handled by the defined handlers inside IIS 7.0, once the specified handlers are executed, IIS 7.0 sends the request to ASP.NET ISAPI extension to be executed!


Hope this post helps you!


May 18 2008

Accessing the ASP.NET Authentication, Profile and Role Service in Silverlight

A great article by Brad Adams on accessing the ASP.NET Authentication, Profile and Role Services in Silerlight!

Check it out here:


Hope you enjoy it!

Tags: ,

May 17 2008

Input Validation Helper Methods

I found a  good resource on validating user input on Channel9. You can reach that resource by following this link:

The page contains a set of utility methods to help you in validating the inputs for your web application. The technique used is "whitelisting" technique in a sense that the user input is validated against a pattern that is known to be good using Regular Expressions.


Hope you will benefit from this page!



Tags: ,

May 9 2008

Install Windows Search Service on Windows Server 2008

Category: Windows Server 2008[email protected] @ 09:04

Enabling advanced search inside Microsoft Office Outlook 2007 requires that you install Windows Search Service on the machine! However, installing this service is not that direct and easy to reach.

To install Windows Search Service on a Windows Service 2008 follow the steps below:

  1. Go to the Server Manager
  2. Click on Add Roles
  3. Select File Services
  4. Select Window Search Service
  5. Select the drives you want WSS to have control on


Hope this helps,