Discussion: SharePointDSC with non-englisch systems or ISOs
See original GitHub issueLately there are a few issues focusing on localization troubles with non-english OSs or SharePoint installs - they are more or less related to #665.
The following issues are related to language issues or use ValueMaps, that will fail with non-english SharePoint setups (tbc.)
Do we have a chance to switch to internal enums? These should be the same across environments.
For example:
namespace Microsoft.Office.Server.Administration
{
[System.Flags]
internal enum UserProfileApplicationUserRights : ulong
{
None = 0uL,
UsePersonalFeatures = 1uL,
CreatePersonalSite = 2uL,
UseSocialFeatures = 4uL,
UseMicrobloggingAndFollowing = 8uL,
All = 15uL
}
}
or in other cases the use of internal names (TypeNames) like @NikCharlebois introduced in #923.
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (15 by maintainers)
Top Results From Across the Web
SPSearchResultSource - Issue with Non-English ...
Version of SharePoint that is used (e.g. SharePoint 2016) ... Discussion: SharePointDSC with non-englisch systems or ISOs #955.
Read more >dsccommunity/SharePointDsc
The SharePointDsc PowerShell module (formerly known as xSharePoint) provides DSC resources that can be used to deploy and manage a SharePoint farm.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have updated SPServiceAppSecurity to validate the specified permission levels against the possible values from SharePoint. Will submit a PR shortly.
This is what I get:
If I don’t set the CurrentUICulture I get this: