How to deploy custom features to upgraded site collections?
Feature masking involves using a new and separate solution package for the same feature for upgraded sites and site collections (when a feature is scoped to a site or site collection). Feature masking allows upgraded site collections to automatically find and use the correct custom feature assemblies.
What are the benefits of host named site collections?
The recommended configuration does not include the following elements: Enabling apps in environments with multiple zones. Mixing host-named site collections and path-based site collections (except the root site collection). Multiple web applications with host-named site collections.
How to deploy PowerShell solution to SharePoint site collections?
The Install-SPSolution PowerShell cmdlet also includes a compatibility-level parameter to deploy the solution package to locations in the root folder that are designated for either SharePoint 2010 mode or SharePoint 2013 mode site collections.
How to create managed paths for host-named site collections?
You have to use PowerShell to create managed paths for host-named site collections. Managed paths for path-based sites apply at the web application level. You can use Central Administration or Microsoft PowerShell to create managed paths for path-based site collections.
Can you add site collections to SharePoint 2013?
It was tested to work in SharePoint 2013 without a change to the code. You know that you can add it to your SharePoint 2013 farm, and it works for users in site collections in SharePoint 2010 compatibility mode and when you upgrade the site to SharePoint 2013.
When to use feature masking in site collections?
Feature masking is not used in this scenario because site collections in both modes use the same code (duplicate feature assemblies located in the corresponding 2010 and 2013 mode folders). The steps for this scenario include the following: Create the solution package containing the custom feature. Add the solution package to the farm.
When to use legacy custom features in SharePoint?
When you use legacy custom features in a SharePoint 2013 farm, you might find yourself in one of the following three situations: The custom feature provided by the solution package currently works for site collections in SharePoint 2010 mode. It also works for site collections in SharePoint 2013 mode.
How to deploy custom features in SharePoint web server?
Use the Install-SPSolution PowerShell cmdlet to deploy the SharePoint solution package to the farm. This unpacks the solution package and copies all files that are contained with a custom feature to a “Feature” directory located on the farm’s front-end web server.