Wow, today marks three years since I started blogging… my blog-o-versary I guess. It still feels like only yesterday I decided to jump on the bandwagon, create a blog and post my first entry: My first blog….

Last week I posted about an issue you’ll run into if you have an existing Publishing Site (aka: WCM site) you created in MOSS 2007 Beta 2 and then upgrade to Beta 2 Technical Refresh.

Here are a few links for developers working with Windows SharePoint Services v3 or Microsoft Office SharePoint Server 2007 Beta 2 Technical Refresh:

David Bailey from RDA Corp clued me into a very slick way to obtain the public key token and blob for a signed assembly directly from within Visual Studio 2005.

Its been almost three years since I started blogging and with the recent flood of posts thanks to today’s release of MOSS 2007 Beta 2 Technical Refresh, I hit the mark of my 1,000th post (this is 1,001).

The release of Beta 2 Technical Refresh for MOSS 2007 brings a very welcomed change. In Beta 2 and earlier versions of MOSS 2007, when you went to edit content in a field control containing HTML, you clicked on the body of the field control which launched a popup where you did your editing.

Earlier today I posted about an issue you’ll run into if you have created a Publishing site in MOSS 2007 Beta 2 (B2) and then upgrade to Beta 2 Technical Refresh (B2TR).

If you’ve created any Publishing sites (WCM sites) in MOSS 2007 Beta 2, you need to be aware of something.

MOSS 2007 (and WSS v3) Beta 2 TR is now available. B2TR is delivered as a patch to B2, so if you don’t already have B2, then you’ll need to obtain & install B2 first.

Previously I posted how I found Invirtus’ VM Optimizer (VMO) product to be a big help with virtual machines in the sense that it made them run much faster and, more importantly, shank the overall physical size of the virtual hard disks.