Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
Important
SharePoint Add-ins reached end of life in SharePoint Online on April 2, 2026. Both SharePoint-hosted and provider-hosted Add-ins are retired and no longer work in SharePoint Online, including government clouds. Add-in development, deployment, and usage guidance is retained for historical reference and for applicable SharePoint Server scenarios, not for new SharePoint Online solutions.
SharePoint Server Add-ins deployed through an on-premises app catalog are not retired by this change. Acquiring SharePoint Add-ins from the public marketplace ended on April 2, 2026 for SharePoint Server.
This retirement does not retire SharePoint REST APIs, CSOM, JSOM, or SharePoint Framework (SPFx). For SharePoint Online, use SPFx for user interface extensions and Microsoft Entra ID for authentication to external applications. See the retirement announcement and Add-in migration guidance.
Summary
The approach you take to configure variations is different in the new SharePoint Add-in model than it was with Full Trust Code. In a typical Full Trust Code (FTC) / Farm Solution scenario, the SharePoint Server-side Object Model (Microsoft.SharePoint.Publishing.Variations) was used to configure variations, and features that executed the code were deployed via SharePoint Solutions.
In an SharePoint Add-in model scenario, you use the SharePoint Client-side Object Model (CSOM) or REST API to configure variations. This pattern is commonly referred to as the remote provisioning pattern.
High-level guidelines
As a rule of a thumb, we would like to provide the following high-level guidelines to configure variations in the new SharePoint Add-in model.
- Use the SharePoint Client-side Object Model (CSOM) API to configure variations whenever possible.
- .Net Client side object model Variations class (MSDN API Documentation)
- JavaScript Client side object model Variations class (MSDN API Documentation)
- Not all variation configuration settings are currently available via the SharePoint CSOM API Variations classes listed above.
- You can go beyond what the CSOM API Variations classes listed above provide and configure some variations settings. To do this, you set the values for variations settings stored in site property bags and/or modify list items in the lists associated with variations.
- The VariationsExtensions.cs class (O365 PnP Sample) contains several examples that modify property bag and list item values to configure variations settings.
- The VariationsExtensions.cs class (O365 PnP Sample) illustrates how to configure all of the settings that you can set in the variations settings page.
- The Choose the languages you want to make available for a site’s user interface (O365 Support Article) addresses some of the multilingual capabilities of Office 365.
Related links
- Guidance articles at https://aka.ms/OfficeDevPnPGuidance
- References in MSDN at https://aka.ms/OfficeDevPnPMSDN
- Videos at https://aka.ms/OfficeDevPnPVideos
PnP samples
- VariationsExtensions.cs class (O365 PnP Sample)
- Samples and content at Microsoft 365 Patterns and Practices (PnP)
Applies to
- Office 365 Multi Tenant (MT)
- Office 365 Dedicated (D)
- SharePoint 2013 on-premises