Although before you get started you need to make sure you have FastCGI and URL Rewrite Module installed on your IIS7.

If you’re missing one of those things, you can check out these guides:

- Using URL Rewrite Module
- Setting up FastCGI for PHP

Once you’ve done that, go to the “Settings” section in your Wordpress admin area and click on “Premalinks”:

On that page, choose the “Custom, specify below” option and enter
“/%year%/%monthnum%/%postname%/” (or any other format of your choosing) in the “Custom structure” text box.

After you save the settings, you’ll notice that all your blog posts will have their URLs in the format you specified earlier. Although if you try to click on one of them you’ll get a 404 – File Not Found error. Thats because we still haven’t told the server where to go when it gets those requests.

To do so, you’ll have to create a Web.Config file (if you don’t have one already) in the same directory as your Wordpress blog. Once you’ve done that, paste the following inside configuration->system.webServer element:

<rewrite>
    <rules>
        <rule name="Main Rule" stopProcessing="true">
            <match url=".*" />
            <conditions logicalGrouping="MatchAll">
                <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
                <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
            </conditions>
            <action type="Rewrite" url="index.php" />
        </rule>
    </rules>
</rewrite>

Click here to download the entire Web.Config file.

That rewrite rule we added above will match any requested URL and if that URL does not corresponds to a file or a folder on a file system, then it will rewrite the URL to Index.php. At that point, WordPress will determine which content to serve based on the REQUEST_URI server variable that contains the original URL before it was modified by the rule.

After you’ve saved the Web.config file, fire up any one of the permalinks in your WordPress blog. If everything went as expected, you’ll see the correct content returned by the web server for every permalink.

1.Open IIS by double-clicking on Control Panel->Administrative Tools->Internet Information Services

2.Right Click on Web Sites->Default Web Site

3.Click on Properties->Home Directory and choose the location of your website

Now lets give the ASPNET account the appropriate permissions to access that directory…

4. Using My Computer or the Windows Explorer, navigate to the folder containing the website you choose in the previous step

5. Right click on the folder and and go to Properties->Security

5. On the Security tab, click on Add to locate the ASPNET account

6. Click on Locations and select the local machine

7. Click on Advanced->Find Now to list all the user accounts on your local machine

8. Choose ASPNET and click on OK. (If you don’t see ASPNET account in there, go to step 11)

9. Return to the security tab. Select the ASPNET user account and check the Full Control checkbox under the allow column. Click OK.

10. Thats it! You should now be able to go to http://localhost/ in your browser window and see your website.

If you don’t see an ASP.NET account in Step 8 then…

11. Run “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ aspnet_regiis.exe -i -enable” in the command line window and then repeat steps 1 through 10.

Following steps are optional. They help you configure your web project to automatically reference the local web-server when you run or debug a site instead of launching the built-in web-server itself…

12. Open Visual Studio and select your web-project in the solution explorer, right click and select Property pages.

13. Select the Start Options from the left navigation, and under Server change the radio button value from ‘Use default Web server’ to ‘Use custom server’. Then set the Base URL value to be: http://localhost/

Now, when you click on any page in the app and then hit F5 or Ctrl-F5, the IDE will use the local web-server instead of popping up its own.