.NET framework has been released a long time ago but ever now and than I receive a question about supportability of a specific SharePoint version with .NET framework 4.8.
So for your reference: SharePoint 2013, 2016, and 2019 are supported with .NET Framework 4.8.
Permalink
Is there any prove in official MS docs that SharePoint 2019 installed on machine with .NET Framework 4.8 are officially supported?
Your statement “SharePoint 2013, 2016, and 2019 are supported with .NET Framework 4.8″slightly contradict with blog header “All Posts provided “AS IS” with no warranties, and confers no rights.
The opinions and views expressed in this blog are those of the author and do not necessarily state or reflect those of Microsoft.” 😉
Permalink
Hi Sergey,
I’m not aware of public documentation of this fact but the information here is reliable.
Cheers,
Stefan
Permalink
Thanks Stefan. Microsoft has announced that 4.6.x and below will be EOL 4/2022. Would it be Best Practice to install 4.8 and remove versions < 4.8 on SP FE and APP servers?
Permalink
Hi,
.NET 4 has inplace upgrade. With other words only the most recent .NET version will be installed on a machine.
Yes, you should upgrade .NET 4 to the most recent version.
Cheers,
Stefan
Permalink
Hi, I know it’s late but, can I simply install 4.8 on the server without rebuilding my applications targeting to 4.8? My applications are targeting 4.5. Thank you
Permalink
Yes.
Permalink
Hi Stefan, I wish I can get you, God willing, I have a question to the related post, what if I have SP 2016 environment using .Net 4.5 framework on application and SQL servers, I have to upgrade to .Net 4.8, in this case, do I have to reinstall SP or I can do it in the same environment? Thanks in advance
Permalink
Hi Muhammad,
no need to reinstall SharePoint for this .NET upgrade.
You can do it in the same environment.
Cheers,
Stefan
Permalink
Thanks a lot Stefan, so to be sure, just download and install .Net framework 4.8 manually without changing anything, God willing, am I right?
Permalink
Yes. Be aware that you should do it in a maintencance window to accomodate for a machine restart.
Permalink
For both SQL 2014 and Application servers?
Permalink
Hi Muhammad, I’m not an SQL expert – so I cannot give you a 100% answer on this.
I would suggest to evaluate this in a test environment before applying in production.
Permalink
Hi,
We Install Office Online Serrver On windows 2022 Itsnt work
We get on Event Viewr err for .Nnet,
Mybe Its problem with .Net Version ?
Permalink
Hi Ari,
you did not specify what error you get during the installation or what exact .NET error you get in event viewer.
Here you can find the prerequisits for Office Online Server:
https://learn.microsoft.com/en-us/officeonlineserver/plan-office-online-server#software-hardware-and-configuration-requirements-for-office-online-server
Please ensure that all prerequisites are fulfilled.
Cheers,
Stefan
Permalink
Hi Stefan
we trying to install SharePoint Server 2019 + December 2023 on Windows Server 2022
we install the .NET from the Microsoft Documentaion , but clean install of SharePoint Server 2019 provide us error in the central Admin Center – loading this assembly would produce a different grant set from other instances 0x80131401 Error – this is from Freash Install
any Idea?
Thanks
Nati
Permalink
Hi Nati,
this is a .NET framework error, not something from SharePoint.
I would suggest to try the solution listed here:
https://stackoverflow.com/questions/42240956/loading-this-assembly-would-produce-a-different-grant-set-from-other-instances
Create a new registry DWORD value called LoaderOptimization and give it the value 1 within the key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework”.
Cheers,
Stefan
Permalink
We have 4.8 installed on our SharePoint 2016 Farm.
We’ve confirmed that the SP apppool is running under 4.8 and all sites and custom code/webparts are running properly.
Questions:
1) When the custom code/webparts are running under the SP site, they would be running under 4.8 (regardless if the custom code project was originally compiled to an earlier version of .NET) correct?
2) if an earlier framework were targeted via web.config settings it would still be using the 4.8 framework which does not contain the original vulnerabilities from earlier versions (such as RCE’s) correct?
Permalink
1) yes.
2) yes.
Permalink
Hi Stefan,
I’m working with one of my clients wherein they are having a few code still written on .net framework 3.5.client wishes to upgrade the framework to 4.8 and SharePoint 2010 to SharePoint 2019.
I’m looking for some pointers to migrate an Code from 3.5 to 4.8, what could be the runtime changes/retargeting changes/breaking changes. It would be of great help if someone could give me a roadmap to address the problem – where to start from, what details to look into etc. I searched a lot and could not get any specific pointer for my use case. Please help.
Thanks in advance!
Permalink
Hi Rama,
for most things CLR 4 is downward compatitible to CLR 2.
Your client should open the project in a current Visual studio version and change the .NET version to 4.8 and try to compile.
There will most likely be problems due to library changes and deprecated calls but thats the easiest way to identify the efforts.
Cheers,
Stefan
Permalink
Hello Stefan, little advice for the upgrade of a cumulative update (January 2025) on a sharepoint 2019 server and the update of dotnet 4.8. Do you know if there’s an order to perform this ?
Dotnet 4.8 before the CU ? or the CU before dotnet 4.8 ? I would say that it’s better to install dotnet firt because when the CU will run, it will use 4.8 and not the version before but just advice for this. (There’s already a an “higher version of .NET 4.6.2” on the server as recommanded by microsoft : https://learn.microsoft.com/en-us/sharepoint/install/hardware-and-software-requirements#minimum-requirements-for-sharepoint-servers-in-a-farm)
Permalink
Hi Victor,
there is no dependency between these two. So both should work.
Cheers,
Stefan