moss - Best practice with SharePoint feature deactivation -


I have a custom SharePoint solution that requires several listing instances on a particular site (SPWB). Now some of these lists are normal, for example the 'Pages' document library, Verus are very special custom lists.

My question is to clean the APCS of Customs to stop the feature (if any). My tendency says that generic lists that can be used by many solutions should be left, but more specific optimization should be cleaned. Does anyone have any experience and / or advice on this type of sceanrio?

It's really hard with a strict rule, because it will depend on your specific solution, but I start with something like this:

Any feature should be removed during activation activation when it is disabled:

  1. An end user And the end users could not have been properly expected
  2. Is not necessarily the other feature, or it causes failure comprehensive solution which does not restrict the reactivation time
  3. After the facility.

I am currently working on this project. We have found a new exception to prevent us from deactivating the facilities we have found that in many cases the activation of facilities is one way. This was primarily because a solution was generally made of many features, and by disabling it became a decomposed into the whole solution.

Often, a site was present only to host the feature, disabling the feature left no purpose for the site.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -