sharepoint
2 TopicsMigrating SharePoint Custom Farm Solution (WSP) from SharePoint 2016 to Subscription Edition
Hello Everyone, We all know that we can migrate SharePoint custom farm solutions (WSP) from SP 2013 to SP 2016 and then to SP 2019. I am trying to find out if there are any official guide documents from Microsoft that provide information on the compatibility and process to migrate SharePoint 2016 Farm solutions (WSP) to SharePoint Subscription Edition (On-Prem). If anyone is aware of any information from Microsoft regarding this, please advise. Additionally, when migrating custom farm solutions (WSP) from SP 2013 to SP 2016, SharePoint takes care of the .NET Assembly redirects. This means that the SharePoint 2013 DLLs will be automatically redirected to the SharePoint 2016 DLLs. In most cases, there is no need to rebuild the source code in .NET 4.6 (Link). Does this redirection mechanism work the same way for Subscription Edition as well? Please advise.SharePoint Subscription Edition JS error After 2022 March Update
Hello everyone, After SharePoint Subscription Edition 2022 March Update installation, Some menus of the Modern Sites' throw js exception via the dev console. For example: Site Information link and Site Permissions link. Home.aspx:1 [Report Only] Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "script-src 'strict-dynamic' 'unsafe-eval' 'nonce-8cc6d271-043f-4ba3-a97f-847340968cae'". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. Home.aspx:1 [Report Only] Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "script-src 'strict-dynamic' 'unsafe-eval' 'nonce-8cc6d271-043f-4ba3-a97f-847340968cae'". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. sp-pages-assembly.js?uniqueId=zAU7Q:105 Uncaught (in promise) TypeError: e.render is not a function at sp-pages-assembly.js?uniqueId=zAU7Q:105 (anonymous) @ sp-pages-assembly.js?uniqueId=zAU7Q:105 Promise.then (async) _isSiteInformationLinkEnabled.window._spLaunchSiteSettings.window._spLaunchSiteSettings @ sp-pages-assembly.js?uniqueId=zAU7Q:105 (anonymous) @ VM197:1 Do you have any ideo to solve this problem? Or am i have to wait April Update?Solved