If You Change the Name of an IIS Application that Contains MCMS Templates, the MCMS Template Breaks

Article translations Article translations
Article ID: 330889 - View products that this article applies to.
This article was previously published under Q330889
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SUMMARY

Microsoft Content Management Server (MCMS) templates reference their template file by using the template file property. The template file property is a Microsoft Internet Information Services (IIS) application (or virtual directory) path that tells MCMS where the template file is located. If you change to the name of the IIS application, the binding of the template to the template file is no longer valid and the template does not work.

For example, if you have a template file in the IIS application WoodgroveNet, and you change the name of the IIS application to WoodgroveNet2, the templates that reference the template file in the WoodgroveNet IIS application cannot function. You must also change the template file property in each of the templates that reference this template file from WoodgroveNet to WoodgroveNet2.

To set the template file property for a template, use Properties for the template in Visual Studio .NET. This can be cumbersome when you must change the template file property in many templates (as in the previous example).

MORE INFORMATION

To make this process easier, use the following sample code to generate a simple command line utility that changes the template file property for all templates from one specified path to a new path.

NoteMicrosoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs.
If you have limited programming experience, you may want to contact a Microsoft Certified Partner or Microsoft Advisory Services. For more information, visit these Microsoft Web sites:

Microsoft Certified Partners - https://partner.microsoft.com/global/30000104

Microsoft Advisory Services - http://support.microsoft.com/gp/advisoryservice

For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Preconditions

  • The computer from which you run this tool must have MCMS installed.
  • To run this tool, you must have MCMS Administrator rights.

Use


CmsFindReplaceTemplateSourceFile /vroot to replace/ /new vroot/ [nosubmit]

Example


The following example will change the file template property to WoodgroveNet2 for all templates that have a template file property that currently begins with WoodgroveNet.

At a command prompt, type the following:
CmsFindReplaceTemplateSourceFile /WoodgroveNet/ /WoodgroveNet2/

Notes

  • Both of the specified virtual directories must start and end with a forward slash ('/').
  • The tool does not support double slashes (for example, '/WoodgroveNet/Templates//').
  • The tool uses the checked out version of the template, if it exists, when the tool matches the virtual directory to replace.
  • Virtual directory matching is case-sensitive.
  • The nosubmit argument is not case-sensitive.
  • If you do not use the nosubmit option, the tool checks in all templates that it changes, regardless of who checked them out previously or whether the templates were in the checked out state when you started.
  • The first time that the tool experiences an error, it stops, and then it tries to roll back all changes.
  • The tool does not fix any references, such as include directives, in template files that may require changes to support the new virtual directory name.
  • The only permitted characters in the virtual directory names are the following: [a-zA-Z0-9 .(){}-_&"'$%@~!^#/] . To use spaces in the virtual directory name, put double quotation marks ('"') around the virtual directory name.

Properties

Article ID: 330889 - Last Review: February 27, 2014 - Revision: 4.4
APPLIES TO
  • Microsoft Content Management Server 2002
Keywords: 
kbnosurvey kbarchive kbproductlink kbdownload kbinfo KB330889

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com