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

When I create a WSP with Deployment Type set to WebFrontEnd and deploy, all of the features contained within are automatically installed. Features that are set up as ActivateOnDefault="TRUE" (Farm or WebApp scoped) or AutoActivateInCentralAdmin="TRUE" thus are also automatically activated simply by deploying the WSP.

The same does not occur when the WSP Deployment Type is set to ApplicationServer. I have to manually install each feature in the WSP one by one from a script. This has been the behavior I've seen in 2007 and 2010, however I have not been able to find this documented as correct anywhere.

Is there a reason this behaves the way it does?

I am using ApplicationServer as my deployment type so that I can package timer jobs and custom central administration pages and custom actions together into one WSP. Should I just continue to maintain deployment scripts that install each feature one by one after solution deployment, or should I use a different approach in packaging?

share|improve this question

Your Answer


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

Browse other questions tagged or ask your own question.