Well, after much procrastination, I finally spent some quality time with the GoDaddy hosting control center and various dasBlog instructions and got it working.
For anyone trying the same...
- From GoDaddy, go to "My Hosting Account".
- Click the [open] link under "Control Panel" for the domain.
- Under settings, select ASP.NET runtime and make sure it's 2.0.
- Under settings, check FrontPage extensions and make sure they are NOT installed.
- Select "Directory Management" under "Content".
- Create a custom directory where you'll host the blog with "Read", "Web" and "Set Root".
- Create the subdirectories SiteConfig and logs and give them each read+write access.
- Create another one called content and give it read+write+web access.
- Download the dasBlog webfiles zip and extract it locally.
- Edit your siteconfig/site.config setting the obvious looking stuff.
- Edit your /web.config to get rid of or comment out the line
<trust level="Medium" originUrl="" /> (a GoDaddy-ism)
- Copy all the extracted files to your blog directory (using explorer view on ftp:// works)
- Point your browser at your blog.
- Sign in using "admin", "admin" (unless you changed the user name in SiteConfig/siteSecurity.config before you uploaded it)
- Immediately change that password.
** Disclaimer: I didn't try those steps exactly so they may not be entirely perfect. **
Edit: Okay, I just setup another blog using those instructions and they seemed to work nicely.
Look here for more help on this.
Now, to blog from Word 2007 with images… create from the blog post template, set up an account of type "Other" and set the Url to http://domain/blogdir/blogger.aspx, set the picture option to "my blog provider". Publish! It should automatically upload pictures to /content/binary/.
Okay, so what is freachable? It is purgatory for .NET objects with finalizers. During garbage collection, objects that have finalizers need to have their finalizers run, but the GC shouldn't have to wait for them (after all the entire process is stalled while GC runs and finalizer code could affect what the GC is doing), but if there are no references to keep the object alive, it will get collected so the object is made to reachable by the finalizer thread by placing it in its special queue called freachable. GC completes and the finalizer thread wakes up, executes the finalizers in the freachable queue, and clears the queue entry, which is the last remaining reference to the object and now the next time GC runs, the object's memory will be reclaimed.
Read all about GC at http://msdn.microsoft.com/msdnmag/issues/1100/gci/
According to that article, it is pronounced f-reachable. That just sounds l-ame.
So what's the point of this blog? To blog stuff I figure out. I will try not to waste bandwidth on "hey, go read what this other guy figured out". Okay, so most of this post is stuff that someone else figured out, but the web.config mod on dasBlog was not in Aakash's notes.