New
#1
Thanks for the info. I can't see any reason there for it to be installed on my two (gaming and work-based) Windows 7 SP1 machines. I'd be interested, however, to see if anyone sees any benefits from doing so.
Today, we are announcing the general availability of the .NET Framework 4.7. The .NET Framework 4.7 was released as part of Windows 10 Creators Update a month ago. You can now install the .NET Framework 4.7 on other versions of Windows.
You can download the .NET Framework 4.7:
The .NET Framework 4.7 includes improvements in several areas:
- High DPI support for Windows Forms applications on Windows 10
- Touch support for WPF applications on Windows 10
- Enhanced cryptography support
- Support for C# 7 and VB 15, including ValueTuple
- Support for .NET Standard 1.6
- Performance and reliability improvements
Please see the Announcing the .NET Framework 4.7 blog post to learn more about each of these improvements.
You can see the complete list of improvements in the .NET Framework 4.7 release notes.
Supported Windows Versions
The .NET Framework 4.7 is supported on the following Windows versions:
- Windows 10 Creators Update (included in-box)
- Windows 10 Anniversary Update
- Windows 8.1
- Windows 7 SP1
The .NET Framework 4.7 is supported on the following Windows Server versions:
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2 SP1
DirectX Dependency
The .NET Framework 4.7 now uses DirectX 11 components for WPF. These components are available on more recent versions of Windows.
You must install an additional DirectX component in order to install the .NET Framework 4.7 on Windows 7 SP1, Windows 2008 R2 SP1, Windows 2012 and Windows 2012 R2. The installation includes a single dll that will get added to your system. It will only be used by WPF applications. It is not possible to install the .NET Framework 4.7 without installing this component.
You can install this component for your operating system:
Please see the following for more information: The .NET Framework 4.7 installation is blocked on Windows 7, Windows Server 2008 R2 and Windows Server 2012 because of a missing d3dcompiler update
Closing
Thanks for trying out the .NET Framework 4.7. Please tell us what you think about the release and how it is working for you in your environment. Please share your feedback in the comments below or on GitHub.
For more information on the release, please see Announcing the .NET Framework 4.7 and the .NET Framework 4.7 release notes.
Source: Announcing the .NET Framework 4.7 General Availability | .NET Blog
Thanks for the info. I can't see any reason there for it to be installed on my two (gaming and work-based) Windows 7 SP1 machines. I'd be interested, however, to see if anyone sees any benefits from doing so.
Can't install because the previous one, "April, 2017 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2" refused to install. "Error 66A."
I hate the security on Win 7. I think it's more trouble than it's worth. ::Sigh:: So how do I get the previous one installed?
So they didn't bundle the additional directx component with the framework 4.7 by default? Damn they're getting sloppy.
I tried installing the d3complier for Win 7, but mine is 64-bit. Now there are 3 things i can't install, sorry, 4. The May Net F is sitting in my Control Panel. Do I need all the framework stuff?
Hi,
Yep I was wondering why creators update was so buggy net 4.7 and messing with direct x11.
BSOD = Watchdog
I think you already know my views on Windows 10. If it weren't for Win 10 I wouldn't have Linux already installed on my new build.