Microsoft MVP Logo

The release of Service Pack 2 for MCMS 2002 includes many bug fixes but also adds support for SQL Server 2005, Visual Studio .NET 2005 and ASP.NET 2.0. The added capabilities of ASP.NET 2.0 adds many new features to the developer's toolbox. As some may have already experienced, working on MCMS 2002 SP2 projects within VS 2005 can be a bit of a challenge. In addition, there have already been multiple problems found with SP2. However, many workarounds have been documented on various resource sites.

The goal of this page is to provide a single, consolidated list of MCMS 2002 SP2 resources. It will not include any pre-SP1 resources, just SP2 related resources. If you have a resource you think needs to be added, let me know by submitting it via my contact form.

So far all credit goes to Stefan Goßner & Spencer's

Resource Categories

Microsoft Downloads, Knowledge Base Articles, & Miscellaneous SP2 Articles

MCMS 2002 post SP2 hotfixes

All links currently point to Stefan's blog, MSFT MCMS Escalation Engineer. I'll amend the links when they are available on

Visual Studio .NET 2005 Installation/Setup

MCMS ASP.NET 2.0 Development

February 13, 2006

Fixed some typos in the original article.

February 15, 2006

Added Stefan's “CrossPostbacks with MCMS 2002 SP2” article

March 14, 2006

Updated links to MSFT Knowledge Base for articles #913400 & #913401 (recently published to

March 16, 2006

Added hotfix 915190 which adds support for VS.NET 2005 w/ CMS 2002 SP2 without requiring VS.NET 2003 to be installed first.

July 11, 2006

Added Stefan's posts about using ASP.NET 2.0 Web Parts in a MCMS 2002 SP2 site & getting MCMS, VS.NET 2005, and Team Foundation Server working together.

August 28, 2006

Updated KB's #913554, 914195, 914782, 915190 to point to the actual KB on Microsoft's site, previously they were just pointing to Stefan's announcement until the KB's were live on the support site. I also added a link to a post where you can get the updated WoodgroveNET sample site, updated for ASP.NEt 2.0.

Comments powered by Disqus