These videos are definitely worth watching because they explain the credit crisis so well and really bring it down to people like me (the non-financial bankers).

Part 1

Part 2

I haven't disappeared.  I have just been really, really busy.  I have also been working on another portion of my website (a small little playground).  Hence, my previous post about stopping the inheritance of web.config's.  Anyway, I will have an update once work slows down a bit.  Developing all day definitely takes a lot out of you.

I've searched the Internet high and low to find the answer to this question: how to have multiple applications on GoDaddy with BlogEngine.Net as the root application.  I have finally found the answer, by slowly figuring it out.  First, we need to create a new IIS Application.  So we will go into GoDaddy's IIS Settings under Content:

Click OK and wait for GoDaddy to setup your new application.  Once that directory is setup, we need to create a web.config to place in that directory.  To do this, I just opened Visual Studio 2008 and created a new website.  That gives a base to work with.  If you do not have Visual Studio 2008, download the base here. (remember to remove the base_ in the file name)

Now that we have a base, we need to remove some of the role providers and modules that BlogEngine.Net includes.  After line 64 add the following line to remove the RoleManager:

<roleManager enabled="false" cacheRolesInCookie="true">
    <providers>
        <clear/>
    </providers>
</roleManager>

A little further down (line 85 for me), you will see <httpModules>.  This is where we will remove all the http modules from BlogEngine.Net.  Replase the <httpModules> section with this:

<httpModules>
    <remove name="WwwSubDomainModule"/>
    <remove name="UrlRewrite"/>
    <remove name="CompressionModule"/>
    <remove name="ReferrerModule"/>
    <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</httpModules>

Save the file and upload the web.config to the application directory you made earlier.  Now any application in your new application directory including sub directories will use your new web.config.  In case my directions were a bit confusing, here is my completed web.config.  This was really frustrating for me, so I hope it helps someone out there.