SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

is there a way to declaratively pass parameters to a feature using activationdependency?

I have a feature defined in ONET.XML that i want to move to a feature stapler, but since it has a property defined I want to retain that in the activation dependency. is this possible to do declaratively?

share|improve this question
up vote 2 down vote accepted

If you mean is it possible to have "per activation dependency Feature properties", then unfortunately the answer is no. You can, of course, have declarative properties on the Feature but I guess that's not what you're asking?

share|improve this answer
I would like to, declaratively, set properties on features either using FeatureSiteTemplateAssociation or FeatureActivationDependency. If not possible, whats my best alternative? – Anders Rask Aug 1 '10 at 20:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.