R – SharePoint / WSS: How to localize a feature

mosssharepointwss

I have a WSP package that contains some features.

I need to be able to localize the following in the features:

Site Column Field Display Names
Description of Content Types
List Instance Description
List Schema Fields

I am looking for a method to achieve all of this as easily as possible.

Best Answer

In short, create a Resources folder inside of your feature folder, then add a text file to it, name it Resources.en-US.txt rename the file from .txt to .resx.

I use this roundabout way because I don't want the .designer.cs file and i don't want the schema part in my resx file. Which is what you get when you add a normal Resources file.

Open the resx file using the xml editor (right click -> open with) and add your properties in the following format:

<root>
  <data name="ANYNAME">
    <value>Some value</value>
  </data>
  <data name="ANOTHERNAME">
    <value>Some value</value>
  </data>
</root>

now you can use $Resources:ANYNAME etc. in your feature.xml i.e.

<feature Title="$Resources:ANYNAME" Description="$Resources:ANOTHERNAME" />

Related Solutions

SharePoint: Content Type ID differs form content type id attached to a list instance

When you create a list based on a content type, each instance of the list is actually a new content type that inherits from the parent.

Take a look at this... http://soerennielsen.wordpress.com/2007/09/11/propagate-site-content-types-to-list-content-types/

Update-Regarding finding the instance of the List without using the name, take a look at the SPContentTypeUsage class also!

R – Timing in SharePoint features deployment

You can also create an event handler and activate the features in the order you want. I've found it always to be better to rely on doing things manually in code rather than using the xml files to do thing.

Take a look at SPWeb.Features and FeatureCollections.Add

Here is an example of how I coded this in my event handler

public void ActivateFeatures(SPFeatureReceiverProperties properties)
{
    logger.Info("Creating content types");
    // feature is scoped at Site, so the parent is type SPSite rather than SPWeb..
    using (SPSite site = properties.Feature.Parent as SPSite)
    {
        SPWeb currentWeb = null;
        if (site != null)
        {
            currentWeb = site.RootWeb;
        }
        else
        {
            currentWeb = properties.Feature.Parent as SPWeb;
        }

        using (currentWeb)
        {
            if (currentWeb == null) return;

            try
            {
                currentWeb.Site.Features.Add(new Guid("01A27C0C-2E44-4298-A74F-8F50601A20B0")); // ctCategory
                currentWeb.Site.Features.Add(new Guid("496DFE3E-A41E-46e8-B627-29775F376017")); // ctChapter
                currentWeb.Site.Features.Add(new Guid("F2ECBD5A-4766-49bf-A158-62550661E141")); // ctChapterList
                currentWeb.Site.Features.Add(new Guid("8C91646F-1466-49d7-BB53-B666F164AA96")); // ctComments
                currentWeb.Site.Features.Add(new Guid("112E1564-FA1C-41fd-853A-F7569C555905")); // ctDocument
                currentWeb.Site.Features.Add(new Guid("48BD5A07-8DD1-46ef-9F05-9824380BA26E")); // ctExternalReviewer
                currentWeb.Site.Features.Add(new Guid("20553A8E-8272-400c-816D-6EE8E02F34E9")); // ctStandard
                currentWeb.Site.Features.Add(new Guid("E84259BD-E4B3-465e-8928-1745F8760F2D")); // ctSuggestion
                currentWeb.Site.Features.Add(new Guid("0B313654-D296-4bfa-8F21-E4FF33C1DD6C")); // ctTask
                currentWeb.Site.Features.Add(new Guid("EFDA877B-B686-4954-9F1A-65ADB32B2E50")); // ctDepartment
                currentWeb.Site.Features.Add(new Guid("4E4B984E-65E2-4601-A216-2C4D08AA97AE")); // ctInnerWork
                currentWeb.Site.Features.Add(new Guid("4D85D4B9-1909-45cd-81C7-CDBB0874492F")); // ctOtherDocuments
                logger.Info("Content types added successfully");
            }
            catch (Exception ex)
            {
                logger.Error("Could not in activate content types.", ex);
            }
        }
    }
}

Best Answer

Related Solutions

SharePoint: Content Type ID differs form content type id attached to a list instance

R – Timing in SharePoint features deployment

Related Topic