Comments

# Sowmyan's SharePoint Developer Blog said on May 29, 2008 1:58 AM:

What is feature stapling and how we can do that in WSS 3.0? You can use Feature stapling to effectively

# A.Coward said on December 23, 2008 10:29 AM:

This is great info, but it doesn't mention where a FeatureReceiver fits in the order.

Presumably it depends on how you've stapled it?

However, I suspect that it might also be random.

For example, you activate publishing in the onet.xml, and then check IsPublishingWeb() in a feature stapled to the template. In this case, it is probably random as to whether this will return true or false based on e.g. what else the server is up to. I certainly seem to be getting random results when I've experimented.

I have seen people add this to their code to get around the issue!!:

bool pubWeb = false;  

while (!pubWeb)  

{  

  if (PublishingWeb.IsPublishingWeb(web))  

  {  

    pubWeb = true;  

  }  

}  

It seems to me that the safest thing is not to mix and match feature activation methods, because you cannot depend on the order they will fire. It's better to choose one place e.g. onet.xml or featurereceiver and put all your activations in one location where you can be sure of the order that they are going to fire.

# Stian Kirkeberg said on January 30, 2009 3:29 PM:

The FeatureReciever events, ie featureactivated, is triggered when the feature is activated, so yes it depends on how you stapled it.

In our SiteConfigurator feature on Codeplex, we have omitted this problem by giving each feature an "order" attribute (integer value), and active the features accordingly.

# UK SharePoint Team (MCS) said on February 18, 2009 12:41 PM:

What do you mean by "quasi random order"?

I'm having an issue in that I have two web-scoped features (Feature A = Several list instances, Feature B = adding a module to one of the lists) which are both stapled to one of the standad Site Definitions.

Feature B depends on Fetaure A. I've put the activation dependancies in but it seems that my stapling feature is trying to activate Feature B before feature A has fully activated and the lists instances have not been created.

However I have had this working, but it seems to have broken since adding a third feature, hence me thinking that somewhere a new sequence has been set in the stapling feature.

# Stian Kirkeberg said on February 18, 2009 1:07 PM:

>> What do you mean by "quasi random order"?

I mean it is not a order you can control 100 %, unfortunately. However I have adressed this issue in our SiteConfigurator tool on codeplex.com - http://www.codeplex.com/spsiteconfigurator

Leave a Comment

Name (required) 

Your URL (optional)

Comments (required) 

  

Enter Code Here: Required

Remember Me?

About Stian Kirkeberg