SharePoint Server 2007 for MCMS 2002 Developers

Introduction to Office SharePoint Server 2007
As a Microsoft Content Management Server (MCMS) 2002 developer, you know that MCMS 2002 proved to be a great product for content management, and you have probably used MCMS 2002 successfully to maintain your sites.

Some of the tasks for MCMS 2002 required the development of custom code that was costly to design, write, and maintain. In addition, repetitive code needed to be rewritten for almost every MCMS 2002 application.

With Microsoft ASP.NET 2.0 and MCMS 2002 SP2, you no longer needed to write code for site navigation, for search integration, or to have more flexibility authoring workflows on each site. Microsoft Office SharePoint Server 2007 unifies content management and collaborative solutions to assist you in creating dynamic, highly customized, content-centric Web sites faster and easier. Office SharePoint Server 2007 default functionality frees you from the routine work of creating custom code for common tasks, and in addition, offers the following new features:

Extensible workflow

Enterprise Search engine

Multilingual site publishing

Recycle bin (new for SharePoint Server)

RSS feeds

Single Sign On

As an experienced MCMS 2002 developer, you can quickly use your Web content management knowledge in SharePoint Server 2007.

You no longer have to deploy a solution based on Microsoft Office SharePoint Portal Server 2003 and a solution based on MCMS because, in SharePoint Server, you can develop a single solution that includes both content management and collaboration capability. SharePoint Server is built upon Microsoft Windows SharePoint Services 3.0 and offers a powerful new API. You have access to built-in Web Parts, lists, document libraries, templates, workflows, and RSS.
This article provides a side-by-side comparison of the development concepts in MCMS and SharePoint Portal Server 2003 with SharePoint Server 2007, to help you get up to speed quickly. This article does not provide code examples or step-by-step instructions for using SharePoint Server, but instead points you to the equivalent SharePoint Server concepts so you can know where to find additional information.

This article provides a side-by-side comparison of the development concepts in MCMS and SharePoint Portal Server 2003 with SharePoint Server 2007, to help you get up to speed quickly. This article does not provide code examples or step-by-step instructions for using SharePoint Server, but instead points you to the equivalent SharePoint Server concepts so you can know where to find additional information.

Terminology Changes
Because Office SharePoint Server 2007 is built on the Windows SharePoint Services platform, MCMS 2002 terminology has changed or been replaced to fit more naturally with its SharePoint foundation.

The following table presents a one-to-one mapping of the main MCMS 2002 elements and their SharePoint Server 2007 equivalents or replacements.
Read More

Customizing and Branding Web Content Management-Enabled SharePoint Sites (Part 3 of 3): Creating and Configuring WCM-Enabled Sites

Introduction to Creating and Configuring WCM–Enabled Sites
Web content management (WCM) is enabled in Microsoft Office SharePoint Server 2007 through a set of features—many of which rely on Microsoft Windows SharePoint Services 3.0—that are discussed in the first article of this series. The second article discussed the extensibility options you have as a developer. (For links to the first two articles in this series, see Additional Resources.) To conclude this series, I take an administrator's approach to WCM. Starting with the steps to create an Internet site, I show you how to configure and tune your site for anonymous access and forms authentication. I also demonstrate how you can create and configure site variations.

Creating a Publishing Portal
A company typically hosts an Internet site in its own site collection and a dedicated Microsoft Internet Information Services (IIS) Web site (a Web application). The steps to create a site are not much different from the steps you take to create team sites or a portal site. You actually make the decision very late in the process at the level of the site template you select. For an Internet site, you select the Publishing Portal template.

Read More

Customizing and Branding Web Content Management-Enabled SharePoint Sites (Part 2 of 3): Extending WCM

Introduction to Extending WCM
Although Microsoft Office SharePoint Server 2007 provides a rich site definition for delivering an Internet presence and Web content management (WCM) infrastructure, most organizations discover the need to customize and extend the default capabilities. In Office SharePoint Server 2007, all of the WCM features and the underlying artifacts are highly extensible.

Understanding the Structure of Master Pages
Each page that a visitor sees in the browser when navigating to an Office SharePoint Server 2007 site is a combination of a master page and a published page based on a particular page layout (a template). The first article in this series (Customizing and Branding Web Content Management-Enabled SharePoint Sites (Part 1 of 3): Understanding Web Content Management and the Default Features) provides a general overview of master pages and page layouts. Let's go further in this article.

Read More

Customizing and Branding Web Content Management-Enabled SharePoint Sites (Part 1 of 3): Understanding Web Content Management and the Default Features

WCM Enhancements in Windows SharePoint Services
Microsoft Windows SharePoint Services 3.0 introduces a number of major improvements to the way you store and manage information and documents in lists and document libraries. Let us first review these improvements because they form the basis on which a lot of the WCM features are relying. Here is the list of enhancements discussed:

General enhancements

Site columns

Extensible field types

Content types

General Enhancements
Versioning of content stored in lists and document libraries has changed significantly in Windows SharePoint Services 3.0. Lists support versioning now, and document libraries let you differentiate between minor (draft) and major (published) versions (Figure 1). The concept of minor and major versions is important in any Web content management system. Minor versions of pages are not exposed to everybody—only to the content authors and visitors of the site with the required permission level. The step from a minor version to a major version is, in most cases, the result of a workflow, but an authorized user can also decide to manually publish the minor version as a major version. Major versions of pages are available to every visitor of the site.

Read More

Designing Your MCMS 2002 Solution for Reusability

Microsoft Corporation
Applies to:
Microsoft Content Management Server 2002

Summary: Use best-practice design recommendations for Microsoft Content Management Server 2002 applications and Web sites to help you create your site in a way that prepares it for future versions of MCMS technology. (8 printed pages)

Introduction
Microsoft recently announced that the next generation of its Web content management technology will be released as part of Microsoft Office "12", the code name for the next version of the Microsoft Office System. The new offering will succeed Microsoft Content Management Server (MCMS) 2002. Office "12" will provide seamless integrated Web content management and portal capabilities that will share a common, scalable architecture built on the next-generation Microsoft Windows SharePoint Services foundation. The new release will provide significant enhancements and new capabilities for page authoring, workflow and approval, content deployment and overall site administration and management. Office "12" is expected to be available in the second half of calendar year 2006.

Read More

Code Samples - CMS and SharePoint Connector Demo

by Bob German
New demo for Microsoft Content Management Server, with or without the Connector for SharePoint Technologies. Includes the following: - Basic CMS authoring, editing, and approval in a real-world design, including the Authoring Connector - Improved authoring experience with the new Telerik r.a.d.editor control for CMS - Flexible navigation based on channels and postings, including ability to modify the navigation via the CMS authoring console - Multi-lingual content and language-agile content templates - Manipulating structured data via XML placeholders Content syndication, both in-bound (via a web service) and out-bound (via an RSS feed and an XML file drop) - Connected postings to a SharePoint site using the CMS Connector for SharePoint Technologies - Publishing XML documents (WordML or InfoPath) from a SharePoint document library to CMS using the CMS Connector for SharePoint Technologies.

How can I make my web site faster with caching ?

Kai Lee, a program manager from the Web Content Management team posted an article about MOSS2007 caching
Read More

Microsoft Office SharePoint Server 2007 Trial Version

This is the x86 release version of Microsoft Office SharePoint Server 2007 Trial for Standard and Enterprise editions.
Read More