Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3947810
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T01:17:46+00:00 2026-05-20T01:17:46+00:00

The 1.0.0.0 version of my Feature’s Template.xml file looked like this: <?xml version=1.0 encoding=utf-8

  • 0

The 1.0.0.0 version of my Feature’s Template.xml file looked like this:

<?xml version="1.0" encoding="utf-8" ?>
<Feature xmlns="http://schemas.microsoft.com/sharepoint/">
  <Properties>
    <Property Key="AvailableWebTemplates" Value="MPS#0;MPS#1;MPS#2;MPS#3;MPS#4" />
  </Properties>
</Feature>

The new version 1.1.0.0 is as follows:

<?xml version="1.0" encoding="utf-8" ?>
<Feature xmlns="http://schemas.microsoft.com/sharepoint/">
 <UpgradeActions>
  <VersionRange BeginVersion="1.0.0.0" EndVersion="1.1.0.0">
   <CustomUpgradeAction Name="UpgradeTo1v1"/>
  </VersionRange>
 </UpgradeActions>
  <Properties>
    <Property Key="AvailableWebTemplates" Value="MPS#0;MPS#1;MPS#2;MPS#3;MPS#4;STS#2" />
  </Properties>
</Feature>

The value of templates is still MPS#0;MPS#1;MPS#2;MPS#3;MPS#4, when the following code runs in FeatureUpgrading:

SPFeatureProperty property = properties.Feature.Properties["AvailableWebTemplates"];
string templates = property.Value;

Why am I not getting the updated property value? Is this the way it is supposed to be?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-20T01:17:47+00:00Added an answer on May 20, 2026 at 1:17 am

    This is indeed the way it is supposed to be:
    A feature has 1 definition and n instances. The code in FeatureUpgrading is used to upgrade the instances.

    The property in your xml updates the feature definition and not the running instances.

    properties.Feature.Properties["MyProp"] gets the property value of the running instance properties.Definition.Properties["MyProp"] gets the value of the property in the feature definition.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

When I run a feature file in RubyMine it will randomly crash with this
The only version-control software I've really used extensively is Subversion. I like git's feature
em-synchrony.rb implements this feature with Fibers but I would go for a non-Fibre version
I am getting error with my feature.xml. It is version 1.2 not available. The
I have the following code snippet in my feature.xml <Feature Id=0c272f81-49c0-440a-a544-677d51a8ffe4 ReceiverAssembly=FeaturedMasterPage, Version 1.0.0.0,
I would like to use feature detection to tell whether the user's version of
I would like to display the version number of a custom Eclipse feature I
In a recent version, forge.prefs was introduced. This feature seems very similar to the
I recently added a feature to a large application written in Delphi (version 2009)
In my old version of TortiseSVN ( version 1.6) I could enable, a feature

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.