From Stephen Forte's WebBlog:

Do you believe that software can change the world? How about the opportunity to work on an application that promises to help accelerate a cure for cancer?

If you or someone you know is passionate about helping to accelerate a cure for cancer, and is in a position to take on a new job, read more about one of the coolest software projects ever. Here's a summary of the requirements:

• Well-rounded skills in software application development.
• One who has been working primarily with C# for at least the past two years, with an additional minimum three years of Microsoft .NET framework application development experience (and preferable some 2.0 and 3.0 experience).
• Familiarity with Object Oriented design methodology.
• A successful candidate will have experience with Windows client application development (.NET WinForms, preferably WPF) and web services.
• Desirable to have experience with SharePoint, preferable Office SharePoint Server 2007, Office Document XML, or other custom Office applications. You should also have experience working within a distributed development team.

Coming from a C++/C# background, one of my main frustrations with VB has been its lack of a true ternary ("?:") operator. In Paul Vick's recent post, he discusses the possible inclusion of a ternary operator in the next version of VB (9.0 - Orcas). Finally the IIF operator will behave like we C#/C++ (or javascript for that matter) folks expect it to. I'm looking forward to it… now if we could only get rid of those pesky line-continuation characters!

Visual Studio 2005 Team Edition for Database Professionals trial edition requires Visual Studio 2005 Team Suite be installed before you install Visual Studio 2005 Team Edition for Database Professionals trial edition.

It makes it pretty tough to use a trial version if you have to buy it first. If I had Team Suite, I "probably" wouldn't be installing the trial…

VisualSVN has been released, and I like what I see. With this version comes visual indicators that show you the status of each file. This, along with support for file/folder deletion, top of an already great feature set including file moving and renaming. This tool integrates seamlessly with the well-known TortoiseSVN, bringing the TSVN experience right into Visual Studio – and then some. This latest release finally brings VisualSVN to a place where I can now whole-heartedly recommend this to any Visual Studio/Subversion user. There is a free trial available, and the license cost is only $19. See the formal announcement on the VisualSVN blog.

Current feature list

• Support for Visual Studio 2003/2005
• Visual status indicators (high-contrast indicators also available)
• File/folder deletion
• File/folder renaming
• Show log
• Repository browser
• Integration with Windows Explorer
• File locking
• Conflict resolution
• Blame
• Update
• Commit
• Diff ("Show Changes")
• Revert
• Patches
• Branch
• Switch
• Merge
• Update to Revision
• Checkout
• Cleanup

How to Blog with Word 2007 and dasBlog

Start by creating a new document using the "New Blog Post" template (New > Installed Templates > New Blog Post)

Initial Configuration

1. Select "Manage Accounts" from the "Blog Post" tab
   

    

2. Create a new account
   
   1. Settings for dasBlog:
      1. API: MetaWebLog
      2. Blog Post URL: http://<blog_root_url>/blogger.aspx
      3. User/Password: Your blog login and password

          

   2. Picture Options
      
      1. Note that I included my FTP username/password in the "Upload URL" path
      2. The "Source URL" will be http://<blog_root_url>/content/binary/

          

Start Blogging

1. Give your post a title
   
2. Write your content

   

    

3. Add style to your content (note that these styles correspond directly to HTML elements)
   

    

4. Stylize your screen shots
   

    

5. Assign categories
   
   

    

6. Publish your content
   

    

7. View the results
   

UPDATE: When blogging about dasblog, make sure that either your image names don't contain "dasBlog" or that you change the content filter for "dasBlog" to be "\bdasBlog\b" (or something similar) so that your images don't end up like: <img src="content/binary/<a>dasBlog<a/>_image_123.png" />