Last month I pretty much hit the bandwidth limit set by my hosting provider. It's a good limit, but didn't expect the site to grow that fast. The options were to buy more bandwidth or compress. I decided to try out compression. I googled and found few links on turning on IIS compression via the metabase. I didn't want to mess with metabase or registry. I narrowed down to looking for a software compression and looked at few solutions, most wanted me to change the code to work with the product. Then I came across HTTP Compression http://www.codeproject.com/KB/aspnet/httpcompression.aspx on Codeproject. I've added the compression and the results are pretty good. Let me know if you are noticing a faster 123-matrimonials.

This is the scenerio - You have a main site, you add a blog at /blog and a forum at /forum. When you run the /blog or /forum you get errors that it's looking for a DLL used by the main site. You wonder why /blog or /forum would need a specific assebly used by main site. The answer is the nested asp.net apps "inherits" web.config from the main site.

How do you prevent it? Here, add <location tag as follows to the web.config of the main site

<configuration>
    <configSections>
        ...
    </configSections>
    <location path="." inheritInChildApplications ="false">
        ... rest of config
    </location>
</configuration>