I originally posted this little titbit in the wcf forums, but since lots of people there did not seem to know about it, I'll post it here again:
The framework 3.0 RC1 install will kill your existing .svc mapping, so you will not be able to communicate with IIS hosted WCF services (.svc). Obvious workaround is to add the mapping again manually. This will be fixed in the next RC.

I hope that helps a few people out there!

Just last Friday, I readied everything to integrate my winfx parts into our main application. I instructed the team on what to do and put the bits on our server.

Now, Microsoft released RC1. Just my luck, but I'm obviously very happy that winfx is progressing!! Get the new SDK as well. And, you're not hip if you're not running Powershell RC1, or use the word 'hip'

This blog certainly is not intended to be a reposting platform for yours truly, but I can't not mention a new tool (source code included) that allows you to inspect the visual tree of any Avalon application and even let's you see events and databinding!

It should prove to be an incredible help while debugging/learning/profiling your WPF applications. Get snoop here, and never look back again

An article has just been published on code project by Josh Smith that should not escape your attention: Piping value converters in WPF.

Basically, he has written a simple class that will allow you to define a group of converters and use it during databinding like so:
    <local:ValueConverterGroup x:Key="statusForegroundGroup">
      <local:IntegerStringToProcessingStateConverter  />
      <local:ProcessingStateToColorConverter />
      <local:ColorToSolidColorBrushConverter />
    </local:ValueConverterGroup>

and then use it like so:

        <TextBlock
          Text="{Binding XPath=@Status,
                 Converter={StaticResource statusDisplayNameGroup}}"
          Foreground="{Binding XPath=@Status,
                       Converter={StaticResource statusForegroundGroup}}" />

This should prove very valuable indeed!