coComment support for CS 2007

If you are one of my two regular readers, you may have noticed that I published many posts regarding coComment. In fact, I published instructions to integrate coComment in original CommunityServer and CS2.1SP1 (for CS2.0 and CS2.1 Keyvan was faster than me [:p])

(if you think I write so much about coComment is because I love it so much, you totally missed the point of my blog)

Anyway, if you follow the old instructions you'll see that there's bunch of script code you have to add to your blog theme. Unfortunately, that solution does not work anymore with CS 2007, because the controls in the comment form are wrapped in a new Chameleon control. I did not see a chance to access the ids of the contained controls and continue the old solution with my limited ASP.NET knowledge.

Instead, I developed another solution. I simply inherited a new control from WeblogPostCommentForm, where I have all access to the contained elements. And up to now I didn't know how easy it is to add some script in your code to be added to the rendered HTML

Long story short, here's my solution for coComment support in CS2007:

Drop the attached ThomasFreudenberg.CS2007.dll into your ~/bin folder.

Open post.aspx of your desired blog theme

  1. Add following line right after the imports:

    <%@ Register TagPrefix="TFr" Namespace="ThomasFreudenberg.CS2007"
        Assembly="ThomasFreudenberg.CS2007" %>
    
  2. Replace <CSBlog:WeblogPostCommentForm> with <TFr:WeblogPostCommentForm>

  3. and </CSBlog:WeblogPostCommentForm> with </TFr:WeblogPostCommentForm>

In fact, for me as a non-web developer that approach seems much more natural to me than adding fancy instructions in the web control.

ThomasFreudenberg.com Upgraded to CommunityServer 2007

This site has been upgraded to CommunityServer 2007 (I guess visitors to my site do know CommunityServer, and they already read the announcements.) Of all all CS MVPs, I am again late to the party [;)]

The upgrade was pretty easy. I spent about 2 hours on it, mainly because of my limited upload bandwidth. However, I had to create a new CS2007 package, because all the cool extensions I used for my old installation are not yet released for CS2007. But don´t worry, the CS MVPs are busy upgrading the CSMVP CSModule package.

I started to create my own theme a couple of weeks ago, but because of lack of time and CSS experience, it´s not finished yet. Therefore my site still looks the same as before.

BTW, Starting with CS 2007 there´s a new distributable called "One-Click Install"?. This package is a kinda XCOPY distribution, using Cassini and a file-based database. It's great for developers because you neither need to configure IIS nor the SQL Server.

Kathy Sierra

Community Comments

Generally I limit my posts to programming stuff, but after I read Kathy Sierra's Death threats against bloggers are NOT "protected speech"? (why I cancelled my ETech presentations) I have to break my habit.

If you don't know Kathy, she's one of my favorite bloggers. Her Creating Passionate Users should not only mandatory for UI developers, but gives insightful views on user experience every developer and manager should be aware of.

This sucks.

Update 1: Scoble stops blogging for one week, because he, as many others, feels with Kathy.

Virtual PC 2007 released

myvirtualmachines Environment variable

Earlier today Microsoft released Virtual PC 2007. Generally this wouldn't be worthwhile to be mentioned on my blog. However, I'll write this nevertheless because whenever I install Virtual PC, I want to customize the path where the files for the virtual machines are stored, and each time I have look up the information how to accomplish that.

By default, Virtual PC's setup creates a My Virtual Machines folder in My Documents. Though the primary HDD of my machine is a 10.000 RMP beast, I have two additional 10.000s combined to a RAID0, and that's a perfect host for my virtual machines.

Luckily, you are able to customize where Virtual PC stores that files. You only have to specify your desired path in an environment variable named myvirtualmachines.

Though it's even documented in a knowledge base article, I know my blog better than the knowledge base so I post it here [;)]