none
Sequence number in feature.xml

Answers

  • There are several different "sequence numbers" found in features. The one in your sample determines "who wins" when multiple features attempt to place a user control in the SPDelegate control. (SmallSearchInputBox in your example).

    In the case of SmallSearchInputBox, the smaller number wins.  Here's some notes on this number: http://techtrainingnotes.blogspot.com/2008/01/sharepoint-smallsearchinputbox-tip.html

     

    Just an FYI, the sequence number in <CUstomAction> elements control the placement in menus. Smaller numbers at the top and larger at the bottom of the menu.

     

     

     


    Mike Smith TechTrainingNotes.blogspot.com
    Thursday, May 27, 2010 8:51 PM

All replies

  • Can't say I have seen actually seen this in a feature.xml file, and according to MSDN docs it is not an attribute of the feature element - so can safely say it is not used. Unless it is part of another element you are adding to the feature.xml file, in which case could you give an example of where you have seen this.
    Read my wiki at www.intheknow.it for more code and tips for developing with SharePoint 2007 & 2010
    Twitter: @starznet

    Technical Architect at Starznet Ltd. WSS/MOSS development and customisation with a primary focus on CMS.
    Wednesday, May 26, 2010 10:08 AM
  • Hi,

    The SequenceNumber is a unique number that identifies the Feature.

    MS has reserved a significant number of these sequence numbers.

    For more information, check this related discussion too:

    http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/33083b31-e5a8-4b3f-b623-98f040a5eeef


    BR, PM
    Wednesday, May 26, 2010 10:29 AM
  • Prasanjit, the post you have linked to is talking about an elements file and event receiver sequence, not about the feature.xml file.


    Read my wiki at www.intheknow.it for more code and tips for developing with SharePoint 2007 & 2010
    Twitter: @starznet

    Technical Architect at Starznet Ltd. WSS/MOSS development and customisation with a primary focus on CMS.
    Wednesday, May 26, 2010 10:34 AM
  • Hi Stuart,

    thanks,

    it is in elementmanifast.xml.

    I have installed 2 features with same sequence no,

    is there any conflicts with this?

    Thursday, May 27, 2010 7:13 AM
  • Why don't you paste your elementmanifest.xml in that way we can give you accurate replies.

    Thursday, May 27, 2010 2:41 PM
  • I have used the sequence no in the past with SharePoint "DelegateControl" placeholders to overwrite an existing control without changing the MasterPage. For example the following element manifest XML will override the WSS v3.0/MOSS 2007 search field with a custom one:

    <Elements xmlns="http://schemas.microsoft.com/sharepoint/">
        <Control
            Id="SmallSearchInputBox"
            Sequence="20"
            ControlSrc="~/_controltemplates/MySearchArea.ascx">
        </Control>
    </Elements>

    I have never used the same sequence no in different features, but I believe if you don't use it in conjunction with a DelegateControl it will not hurt you.

    Hope that helps!


    Cheers,

    Sig Weber

    If you want a smart answer, ask a smart question http://catb.org/~esr/faqs/smart-questions.html

    Smart developers always view source.

    Thursday, May 27, 2010 7:44 PM
  • There are several different "sequence numbers" found in features. The one in your sample determines "who wins" when multiple features attempt to place a user control in the SPDelegate control. (SmallSearchInputBox in your example).

    In the case of SmallSearchInputBox, the smaller number wins.  Here's some notes on this number: http://techtrainingnotes.blogspot.com/2008/01/sharepoint-smallsearchinputbox-tip.html

     

    Just an FYI, the sequence number in <CUstomAction> elements control the placement in menus. Smaller numbers at the top and larger at the bottom of the menu.

     

     

     


    Mike Smith TechTrainingNotes.blogspot.com
    Thursday, May 27, 2010 8:51 PM
  • Mike, thanks for reminding me again on the CustomActions feature sequence number. I've used it with several features over the past couple of years but just have forgotten about it ;-)

    Cheers,

    Sig Weber

    If you want a smart answer, ask a smart question http://catb.org/~esr/faqs/smart-questions.html

    Smart developers always view source.
    Thursday, May 27, 2010 9:10 PM