Windows SharePoint Services 4.0 named and breaking changes

In the first vNext news since my SharePoint 2010 post, Microsoft has identified Windows SharePoint Service 4.0 by name in a CustomListView knowledge base article. In addition, the Pre-Upgrade Checker that links to the Knowledge Base Article naming the new version identifies a number of breaking changes.

Breaking Changes

Avoid Custom List Views

Gary Lapointe’s analysis suggests avoiding custom list views in Features as they may break.

Custom Field Type Warning

Also from Mr. Lapointe, "if you are creating custom field types and using custom CAML in the RenderPattern element you will have to reset that element to use XSLT after the upgrade completes."

Large Lists may not function correctly

The Large Lists Article reconfirms the practice of avoiding large lists. The details on how many items flag the rule are not in the article. We may have to wait for the spring 2009 arrival of Service Pack 2 for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 to apply the rule to test the limit.

Do Not Add Custom Workflow Actions in WSS.ACTIONS

Custom Workflow Actions stored in the file WSS.ACTIONS will be overwritten in WSS v4. Pre-Upgrade Checker will warn if .actions files exist that may need to be redeployed if upgrading to new hardware. See the SharePoint Designer Team Blog for more info on custom activities.

Track Web.Config File Changes

Web.config files will be replaced with new versions and "all modifications will be lost." See 956499.


Microsoft sites


Broken Glass Image courtesy Rich Anderson Some rights reserved

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.