[part 3] [Upgrade Your Old Customized Templates from WSS2.0 to WSS3.0] Constructing WSS Upgrade .xml

  • Article

once i was involved in an upgrade/migration project for WSS / MOSS

and i faced some difficulities constructing the upgrade file,,

Case: 

In the file WssUpgrade.xml which is found in: “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Config\Upgrade”

 

<  <List FromTemplateId="104" ToFeatureId="00BFEA71-D1CE-42de-9C63-A44004CE0104" />

 

I already know from SDK that:

Attribute

Description

FromTemplateId

Required Integer. Specifies the list definition to be upgraded.

ToFeatureId

Required Guid. Specifies the ID of the content type feature to which the old list definition is upgraded.

v3Type

Required Integer. Specifies the content type ID to which the old list definition is upgraded. Example: v3Type="0x0104

Also,

                                             <File FromPath="{LocaleId}\STS\default.aspx" ToPath="SiteTemplates\STS\default.aspx" />

 

                                I found there are many things listed such as: announce, contacts, custlist, discuss, … etc

 

 

  1. How to figure out what is the value “104” in the FromTemplateID attribute? 

 in v2, list template id is the id you assign for your custom list, it is part of the site definition, and defined in the onet.xml file under list definitions section.

  1. How to figure out what is the value “00BFEA71-…-104” in the ToFeatureId attribute? 

 in v3, most of the custom templates are implemented as “features” therefore you would need to create your custom v2 list or library template as a “feature”. As a best practice, you need to create and test your features before running an upgrade. You need to deploy your feature and use its ID as the ToFeatureId.

  1. In the SDK there is a required field called v3Type but in the xml template it is not there! Why is that? Or which one to follow? [Ferla] use the OOB upgrade definitions provided.. They are used to upgrade the OOB v2 sites so you should be covered.
  2. In a general, do I need to create this file manually? Or is there is a tool that does that for me? [Ferla] Yes, you need to create it manually. I’ve heard of some plans to create a tool for this but I haven’t seen it yet.
  3. How do I know the list of thing (such as announce and contacts) that I should take care of? Shall I take it from the prescan tool? Or whatever I want to maintain after migration? [Ferla] You have to provide an upgrade definition for content you need to migrate to v3. Prescan will tell you the custom site defns used so yes, that’s the way to go..