Microsoft MVP Logo

Next week Penton Media is hosting the Fall 2006 edition of Dev Connections at Mandalay Bay in Las Vegas. There are actually a few conferences: Office Connections, Visual Studio Connections, ASP.NET Connections, SQL Server Connections, Mobile Connections, and SharePoint Connections. I'm presenting three sessions at SharePoint Connections all related to Web Content Management in MOSS 2007:

  • HDV201: Building an Internet Site with Web Content Management in MOSS 2007: Part 1 Wednesday, November 8, 2006 @ 11:30a - 12:45p Web Content Management (WCM) is a new addition to the upcoming release of Microsoft Office SharePoint Server 2007. In part 1 of this session, we'll take a look at WCM and how it fits within Microsoft SharePoint Server 2007. Then we'll dive in and take a look at what's involved in using WCM to host, author, and manage an Internet-facing content site as well as using SharePoint Designer 2007 to build master pages and custom page layouts (demos: creating & working with master pages & page layouts).
  • HDV302: Building an Internet Site with Web Content Management in MOSS 2007: Part 2 Wednesday, November 8, 2006 @ 2:15p - 3:30p Web Content Management (WCM) is a new addition to the upcoming release of Microsoft Office SharePoint Server 2007. In part 2 of this session, we'll build off the site we created in part 1 and dig deeper by taking a look at building field controls, ASP.NET 2.0 master pages and web parts, incorporating custom navigation controls, and building custom workflows. At the end of these two sessions, you will walk away with a good understanding of what WCM is all about as well as what's involved in building and managing Web sites in Microsoft Office SharePoint Server 2007 (demos: building and using a custom field control, customizing navigation via the browser, markup, and how to deploy and utilize custom code solutions, building workflows with SharePoint Designer 2007 and deploying workflows authored in Visual Studio 2005).
  • HDV203: Migrating Your Content Management Server 2002 Sites to Web Content Management in MOSS 2007 Thursday, November 9, 2006 @ 8:00a - 9:15a Web Content Management (WCM) in Microsoft Office SharePoint Server 2007 is a significant upgrade from Content Management Server 2002 (CMS). In this session, we'll briefly look at the significant improvements in WCM over CMS as well as terminology and technology changes. Microsoft has provided a few options for moving your content, templates, and code from CMS to WCM; we'll cover all these options in this session. Then we'll dive into preparation: how can you prepare your new or existing CMS implementations for easy upgrade to WCM. Finally, we'll look at the process of migrating CMS sites to WCM. Most CMS sites won't migrate to WCM with the magical click of a button. We'll cover what is automatically migrated into the new platform and then what post-migration steps you'll need to take to get your site up and running in the new platform (demos: CMS Assessment Tool, content migration profiles).

I'll post the slide decks and code I do in my demos on my speaking page sometime later in the week. I'm also hoping to release a new version of my STSADM Custom Commands for WCM sometime next week... adding more commands (mainly for a better developer experience), fixing a memory management issue in the existing PublishAllItems command, [added 11/3/2006 @ 10p] and adding considerable unit testing[/]. At that time I'll also release the source code for the whole project (it's in the midst of a lot of refactoring and adding unit testing via MbUnit).

If you're interested in talking about MOSS 2007, WSS v3, WCM, or MCMS->WCM migration... please feel free to look me up (or contact me by posting a comment to this post)! Can't find me? Hint: look for the blackjack tables in my favorite casinos (Mandalay Bay, Bellagio & Wynn).

[Update 11/3 12:45p] Almost forgot, I'm also working the Microsoft MOSS Demo Booth Thursday from 12:30-2:15p so feel free to stop by if you want to see and talk more MOSS WCM / Publishing!

Comments powered by Disqus