Orphaned Features

Apr 21, 2011 at 9:29 PM

Due to the simplified retraction process, is it possible to get orphaned features.

This happens in the following scenario:

  • Deploy a web app, site collection, site(s), and a solution and activate a feature from that solution within a site
  • Set the web app to not reatract but set the solution to retractable.
  • Run a Retraction

This will keep the site collection and sites and the feature intact however it will retract and remove the solution. This makes it difficult to work with the feature, redeploy the solution etc... and basically makes things unstable.

To fix this set the web application to retract and it delete everything. Or don't retract the solution before deactivating the feature (manually).

Future release will look at how to handle more complex retractions.