In previous versions of the .NET Framework, WPF applications cannot accept focus tracking without disabling WPF pen / touch gesture support. As a result, WPF applications should rely on you to choose between full WPF touch support or Windows mouse upgrade.
To support the latest use of high DPI and hybrid DPI environments for WPF applications, WPF in .NET Framework 4.6.2 provides per-trace recognition. For more information about getting your WPF application to become a per-monitor DPI-enabled state, see Examples and Developer Guide on GitHub.
In earlier versions of the .NET Framework, WPF applications were system DPI-enabled. In other words, the user interface of the application is scaled appropriately by the operating system, depending on the DPI of the viewer with which the application is processed.
For applications running under .NET Framework 4.6.2, you can disable PER-monitor DPI changes in WPF applications by adding a configuration comment to the section of your application configuration file in
Starting with the WF .NET Framework 4.5, it supports C # expressions in both the Visual Studio designer and code workflows. The rehosted Workflow Designer is a core feature that allows a WF to be in an application other than Visual Studio (for example, WPF). Windows Workflow Foundation provides the ability to support re-hosted Workflow Designer C # expressions and IntelliSense. For more information, see the Windows Workflow Foundation blog.
Availability of IntelliSense when a customer rebuilds a workflow project from .NET Framework versions prior to Visual Studio 4.6.2, WF Designer IntelliSense breaks down when a customer rebuilds a workflow project from Visual Studio. Although the project compilation was successful, workflow types were not found in the designer, and IntelliSense warnings for missing workflow types appear in the error list window. .NET Framework 4.6.2 fixes this problem and makes IntelliSense available.
Machines with FIPS compliance mode enabled can now successfully run a workflow version 1 style application with workflow monitoring. To enable this scenario, you need to make the following change in your app.config file:
If this scenario is not enabled, running the application continues to throw an exception with the message, “This application is not part of the Windows platform FIPS-validated cryptographic algorithms.”
Workflow Designer, flowchart event designer, and other Workflow activity designers now successfully load and display saved workflows after calling the method DynamicUpdateServices.PrepareForUpdate. On versions of the .NET Framework prior to .NET Framework 4.6.2, installing an XAML file in Visual Studio for a workflow that was saved after calling DynamicUpdateServices.PrepareForUpdate can cause the following issues:
Flowchart event designer or other Workflow activity designers can view all objects in their default positions, unlike the added property values.
ClickOnce has been updated to support TLS 1.1 and TLS 1.2 in addition to the 1.0 protocol that it already supports.