Tag Info

New answers tagged

2

You cannot update existing Content Type (or list) definitions by installing updated feature that contains updated definitions. You need to add custom code that is run when feature is activated and which updates existing content type and list. The new content type/list definition pair you can add using the same method you did for the first ones earlier - but ...


0

You can use PowerShell to find this information function Get-SPCustomAction { trap [Exception] { continue; } cls $null = [system.reflection.assembly]::loadwithpartialname("Microsoft.Sharepoint") $null = [system.reflection.assembly]::loadwithpartialname("Microsoft.Sharepoint.Administration") $null = ...


1

AFAIK no. If you deploy a web scoped feature to 'site collection', it will be actually deployed to root web of a site collection. It will still be accessible through Site features link in Site settings, and not through Site collection features link. Force flag has nothing to do with the scope.


0

Using Install-SPFeature cmdlet try to Force install the feature. The Install-SPFeature cmdlet installs a specific SPFeature by providing, in the Identity parameter, the relative path from the version-specific common FEATURES folder to the feature. http://technet.microsoft.com/en-us/library/ff607825%28v=office.15%29.aspx


3

No if you use List Definition with List Instance element, you can set the list instance property Deployment Conflict Resolution=None and your list instance will not be deployed (or not replaced with a new one). The list instance will only be created if it doesn't already exists. If it exists nothing will happen, nor the items will be touched.


0

Feature activation from UI uses the current user context. You can use elevated code if you want normal users to gain more privileges.


1

This is by design. SharePoint will not remove those libraries. You can manually remove those and it will not cause any problems. Later if you activate the Publishing feature will create those if it doesn't exists.


0

Victor Wilén did a pretty good writeup on the SharePoint project that I have found applicable in my work situtations. The template was an output of a collaborative conference, held in London couple of years ago. THe creation of the template involved several Microsoft MVP's, including: Andrew Connell, Ben Robb, Eric Schupps, Matthew McDermott, Mirjam van ...



Top 50 recent answers are included