Optimizely XML Resource Builder

Optimizely XML Resource Builder is a Visual Studio extension that creates Optimizely language resource XML from content type classes in a selected project.

It is useful when a project has many page types or block types and you want a quick starting point for ContentTypes-en.xml, without manually copying every display name, description, and property caption.

Requirements

• Visual Studio 2022 or later
• An Optimizely CMS project containing C# content type classes
• .NET Framework 4.5 or later, which is normally already present with Visual Studio

Installation

1. Close Visual Studio if it is running.
2. Download OptiXMLResourceBuilder.vsix.
3. Double-click the VSIX file.
4. Select the Visual Studio instance where you want to install it.
5. Start Visual Studio.

Generate a language resource file

1. Open your Optimizely solution in Visual Studio.
2. In Solution Explorer, right-click the project that contains the content types.
3. Select Build Optimizely XML Resource File.
4. Review the settings and select OK.
5. The extension writes ContentTypes-{language}.xml to the selected output folder.

By default, the output file is Resources\Translations\ContentTypes-en.xml within the selected project.

If no matching content type classes are found, the extension shows an error and does not create an XML file.

Settings

Attributes

This is a comma-separated list of content type attributes to look for. The default is:

SiteContentType, ContentType

Classes decorated with any of these attributes are included. You can add your own attribute names, for example:

SiteContentType, ContentType, MyCustomContentType

You can enter names with or without the Attribute suffix and without square brackets.

Language code

Sets the language identifier and output file name. For example:

en
sv
fr

Exclude prefixes

Enter a comma-separated list of property-name prefixes to exclude. For example:

Seo, Meta

This excludes properties such as SeoTitle and MetaDescription.

Keep original case

When selected, display names and property captions retain the exact case defined in your code.

When cleared, captions are converted to sentence case. Acronyms written in uppercase, such as CTA, HTML, PDF, and URL, remain uppercase.

For example:

Content type <name> values always use title case, while preserving uppercase acronyms.

Output folder

Enter a project-relative folder, such as:

Resources\Translations

You can also use Browse... to choose an absolute folder. A leading single slash is treated as project-relative, so \Resources\Translations\ is safe to use.

Overwrite existing XML file

This option is off by default.

When it is off, the extension adds only missing XML entries. Existing content type entries, captions, help text, descriptions, and names are preserved.

When it is on, the existing output file is replaced with freshly generated XML.

Generated XML

For each matching content type, the extension reads:

• DisplayName and Description from the content type attribute
• Display(Name = ...) and Display(Description = ...) from properties
• Properties inherited from custom base classes in the project

Properties from custom base classes are written once under icontentdata, which makes shared page or block settings available to all content types.

Example:

<contenttypes>
  <icontentdata>
    <properties>
      <metadescription>
        <caption>Meta description</caption>
      </metadescription>
    </properties>
  </icontentdata>
  <articlepage>
    <name>Article Page</name>
    <properties>
      <heading>
        <caption>Heading</caption>
      </heading>
    </properties>
  </articlepage>
</contenttypes>

Saved settings

The extension saves values after you select OK. They remain available after closing and reopening Visual Studio, and are separate for each solution.

Settings are stored beside the solution at:

<solution folder>\.vs\OptiXMLResourceBuilder\settings.xml

Troubleshooting

The command is not visible

• Ensure you right-click a project, not the solution or a folder.
• Confirm that the VSIX is installed in the same Visual Studio instance you are using.
• Restart Visual Studio after installation.

No content types are found

• Confirm the selected project contains the C# content type files.
• Check the attribute names in the Attributes setting.
• Add custom content type attribute names to the comma-separated list.

A shared base-class property is missing

• The base class must be defined in the selected project.
• The property must have a Display attribute.
• The property name must not match an excluded prefix.