Jonas Kristoferson (1/13/2016)
I know that I need to install .Net3.5 on a WS2012 before installing SQL.
But why is there a need for .Net3.5 ??
Why isn´t newer versions of .Net enough ? 🙂
Is it that the code isn´t updated, just new features added to the newer SQL versions ??
I believe, it's the safest and easiest way to maintain backward compatibility....
The .NET Framework 4.5 and its point releases are backward-compatible with apps that were built with earlier versions of the .NET Framework. In other words, apps and components built with previous versions will work without modification on the .NET Framework 4.5 However, by default, apps run on the version of the common language runtime for which they were developed, so you may have to provide a configuration file to enable your app to run on the .NET Framework 4. All this means more work and testing for sql dba that have to test more in details all applications and assemblies... , if the problem is with an application, you will need to find some dev resources to try to fix this issues and so on... all of the sudden, upgrading to a new version of sql became a nightmare or at least not that easy, innit?
"In practice, this compatibility can be broken by seemingly inconsequential changes in the .NET Framework and changes in programming techniques. For example, performance improvements in the .NET Framework 4 can expose a race condition that did not occur on earlier versions. Similarly, using a hard-coded path to .NET Framework assemblies, performing an equality comparison with a particular version of the .NET Framework, and getting the value of a private field by using reflection are not backward-compatible practices. In addition, each version of the .NET Framework includes bug fixes and security-related changes that can affect the compatibility of some apps and components."
Note. Assemblies are DLL files used in an instance of SQL Server to deploy functions, stored procedures, triggers, user-defined aggregates, and user-defined types that are written in one of the managed code languages hosted by the Microsoft .NET Framework common language runtime (CLR), instead of in Transact-SQL.
I think, you now appreciate the little step of adding .NET 3.5 to your server