raise base .NET Framwork of CM from 4.0 to 4.6.x
currently all file system operations only accept filepaths with maximum length of 256 chars which is related to the used .NET Framework within CM.
Starting with .NET 4.6 this limitation is now raised to 32.767 chars which is very usueful if you for eample manage driver and driver packs, applications and so on per script and file systems within a domain network. (Servernames FQDN could be longer than 8 chars in our case at minumum 30 chars)
You might as well update smsexec to use .Net 4.6.2 instead of 4.0 and we will (probably) never run into path too long issues with driver packages :-)
I guess what Maanavi want to say is : please do not use your own outdated .Net frameworks, when you release new SCCM versions.
Example : Our company is moving to Modern Deployment with Intune/SCCM for our Win10 fleet, and we have to install this old .Net 3.5, in order to run your SCCM Software Center...
Why do we need to install .Net3.5 in 2018 on Win10 machines, to create even more mess on such devices? Is there no way to can keep your Software Center app, aligned with your own recent .Net versions? Win8 had .Net 4.5 already by default...
AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) commented
Can you expand on what you are asking for here?
.NET 4.6 contains all .NET 4 and up functionality.
Maanavi Bisaria commented
Please provide .net 4.6 compatibility from SCCM 2012 r2 sp1 onwards in https://technet.microsoft.com/en-us/library/mt589738.aspx