Hot answers tagged feature
An easy way would probably be to create a timerjob which: Iterate through your webs and find Doc Libraries with specific name. Iterate through the documents to find an column with expired date, use lambda. Mail targeted groups/users for the specified document. As long as the timerjob doesnt run all the time you can minimize the workload.
Welcome to SharePoint Stack Exchange! In your Visual Studio 2012 SP Solution: Enable Always Force Install to True in for your feature. See example below: By default, it is set to False. You can configure that to be set to True.
I guess the reason is, SharePoint app have web scoped feature [you can not change it,because app is nothing just a 'web'] and your web project have some different feature scope. Better solution if you have webscope app based functionality then choose app project and if it is required then only you link up your app with web project by Properties-->Web ...
SharePoint feature driven groups are "to-be-used" for "so-and-so" purposes and they are "not" responsible for the working of the entire site. To elaborate this further "to-be-used" groups are the ones you have mentioned in your question that are enabled by SSPI. These groups have certain permission levels for the current site. For an impact analysis ...
Content type deployed from feature will be removed from server automatically during feature deactivation, but only if it is not used anywhere (including lists and items in SP recycle bin). So, you don't need to remove it manually and actually, you can't remove it programmatically or in any other way except deleting from database (which is definitely not ...
Only top voted, non community-wiki answers of a minimum length are eligible