Thema: .NET Framework ...

[SiLæncer]

Whats new:>>

Added support for cleaning up the .NET Framework 4.6. Updated tool to allow it to differentiate between Windows 8.1 and Windows 10.

http://blogs.msdn.com/b/astebner/

[SiLæncer]

Changelog

CLR:
Ngen emits debug section mapping IL to native [145669]
ICorProfiler implementations can apply metadata changes during rejit [145801]
ICorProfilerInfo API gives access to PDB content for dynamic assemblies, so profilers can show source for callstack frames [145817]
Fixed a x64 JIT bug in exception handling [93398]
Windows runtime metadata export tool allows for major assembly versions greater than 255 [101784]
Fixed out of order execution caused by byte packed class optimization [114744]
CLR writes inner exception information to event log for unhandled exceptions [119369]
Access violations are easier to debug [119373]
Fixed access violation caused by incorrect spill reload of putarg_reg(this) [134106]
Improved performance in EventSource manifest generation [134302]
Check for OS AVX support before using AVX instructions [105782]
Build properly fails when referring to non-generic EventHandler in public surface in managed winmd components [121641]
Fixed a memory leak in native CLR CBindingInput [121931]
Fixed a crash on attach/detach with IntelliTrace [141847]
Windows runtime metadata export tool allows for C# UAP WinRT project to reference a C++ UAP WinRT project that references the mobile extensions SDK [142092]
Fixed stack overflow in System.Numerics [143951]
Fixed bad value numbering for pointer math leading to incorrect CSE optimization [143960]
Fixed RyuJIT back-compat issue [143967]
Fixed a case where a function could get passed a 2^32-1 parameter value instead of -1L [144065]
Fixed a crash in dynamic methods using generic value type parameters [145137]
Fixed a memory leak in mscoreei!RuntimeRequest::ComputeVersionStringThrowing [145389]
Fixed garbage collection dependent handle ages [145686]
Fixed exception handling scopes for IL generated by Roslyn [145835]
Fixed incorrect result with RyuJIT and VS 2013 compiler optimizations turned on [145846]
Fixed garbage collection access violation in heap expand in corner cases due to slightly off pad ratio [145905]
Fixed app packaging resource indexer write access violation at mscoreei!ShimUtil::ReadFileVersion [147707]
Fixed missed cast during binary XOR operation [142659]
Profiling event listener sees enums as names rather than numbers [142794]
Fixed optimization that was incorrectly using a register value for a member variable [142798]
Fixed bad codegen caused by turning on GSCookie check [145632]
Fixed access violation in Compiler::fgValueNumberBlock while jitting [145643]
All floating point reg-to-reg moves use movaps instead of movss/sd [145776]
Added a way to facilitate specifying the ratio of compacting vs sweeping GCs [145709]
Free list damage count isn't incorrectly overwritten [145712]
Improved performance of x64 RyuJIT [145718]
Mitigated "insufficient memory within specified address space range" errors [145720]
Fixed unnecessary decommit on the ephemeral segment [145768]
Fixed an access violation in VB Jit32 codegen when accessing an array expanded by ReDim [142485]
Improved hash function for float and double in value numbering [142492]
Fixed an incorrect Assertionprop optimization on legacy x86 JIT that changes a negative zero into a positive zero and impacts the 32-bit Roslyn compiler [142253]
Improved performance of parallel binary file deserialization [141896]
Fixed an issue with F# applications that target FSharp.Core 3.1 and .NET 4.5.2 causing a FatalExecutionEngineException when deployed to a machine with .NET 4.6 installed [142619]
Fixed an issue with x64 POINTF structure passing during a tail call [145688]
Fixed an issue with !sos.heaptat always looking for unrooted information regardless on if the -iu switch is passed [145696]
EventLog entry displays the exception type and stack trace string in the proper order [145642]
Fixed a bug that prevented users from using NGen on non-Microsoft signed assemblies [147703]
X509Certificates now support Elliptic Curve Digital Signature Algorithm (ECDSA) [145702]
Fixed an issue that caused local variables not to show up in X++ Debugging [145571]
Fixed RyuJIT optimizer causing incorrect result [110557]
BCL:
System.Diagnostics.Process v4.1.0.0 supported in desktop implementation assemblies [142838]
System.ServiceProcess.ServiceController exposes a StartType property [145866]
SqlClient has retry logic for cloud service connection opening [145878]
SqlClient has improved multi-subnet failover connection behavior for AlwaysOn [117760]
HttpListener API exposes TlsUnique to support token-binding [141263]
Enhanced the ECDsa RedZone API [142405]
No overflow exception when using Level in an EventSourceListener on a Write [94974]
No null reference exception when calling EventSource.GenerateManifest(Type, string) when an event method name ends with "Stop" [129244]
Added a timeout to HttpOutput when sending a message [130240]
More reliable connection of TCP local host with named SQL instance [130340]
Vector2/3/4.CopyTo throws the right exception when a null array is passed in [131600]
Vector2/3/4.CopyTo doesn't cause access violation when used with a negative startIndex parameter [142102]
Vector.CopyTo throws consistent exceptions when running with JIT intrinsics [142413]
Fixed access violation in Vector.CopyTo on an AVX2 machine [146428]
Fixed SIMD Vector.Equals on AVX [133633]
Vector3.Dot doesn't cause access violation when value is not stored [142555]
Vector4 constructor evaluates argument list left to right [142843]
Optimized memory usage by HttpListenerAsyncEventArgs [109754]
Fixed a null reference exception in XML validation [111660]
AppContext.BaseDirectory is configurable [142857]
Fixed Serbian culture date parsing issue [144893]
Fixed Norwegian culture date parsing issue [145872]
TransparentNetworkIPResolution works with more than 64 IPs in DNS [147652]
SqlBulkCopy works for data movement from encrypted to plain text nchar columns [149383]
Transparent network IP resolution works if TCP protocol isn't explicitly defined [149824]
Enumerating cultures yields both Persian languages [145823]
An archive created with System.IO.Compression.ZipFile.CreateFromDirectory preserves directory structure when unpacked on OSX [142220]
SqlClient always encrypted supports hardware-protected keys [116442]
Added support for Token Binding for server-side usage of HttpListener [119817]
Uri constructor doesn't throw ArgumentOutOfRangeException when parsing certain URIs with escaped international characters [123235]
Fixed a bug that prevented some localized text from displaying properly [145634]
Fixed a bug that caused the Exception Catch event to get the incorrect source line [142525]
ASP.NET:
TreeNode.ImageTooltip is rendered as title attribute [101518]
Access to WebAdminFiles re-enabled [144513]
Fixed 4.6 regression in DataBoundControl.PerformSelect() [145931]
MaintainScrollPositionOnPostBack works with zoom on Chrome [120243]
RegEx can be opted out for EmailAddresses, Phone, and URL attributes [142685]
Added a MatchTimeout property to RegularExpressionAttribute [142685]
WPF:
Listbox items can be selected by touch on high precision touch panel [141237]
Underline can be applied after strikethrough [141662]
Fixed a crash in XAML in Xceed.Wpf.Toolkit [141966]
ListCollectionView with NewItemPlaceHolderPosition.AtBeginning removes the last element, not the one before it [93418]
Fixed an app hang case when scrolling [99716]
SelectedItem property in DataGrid and UI are in sync even when the selected item is off-screen [117243]
Fixed an exception in System.Windows.Documents.ImmComposition.OnGotFocus [117523]
Adding an object to the end of a collection causes correct argument to be passed to VirtualizingPanel.OnItemsChanged [130980]
TextRange.Save using DataFormats.Rtf exports the last block from FlowDocument [131881]
Fixed leak of ImmComposition objects in System.Windows.Documents.ImmComposition.GetImmComposition [133134]
Fixed a hang when scrolling TreeView with large indent [141179]
Calling window.open from WebBrowser control doesn't result in access denied script error [141608]
Fixed layout when item-scrolling TreeView [122337]
Adding an item to CompositeCollection doesn't cause ItemsControl.SelectedIndex to incorrectly increment [122826]
Glyph elements containing alphanumeric characters aren't always printed using MS Sans Serif [142597]
VisualTreeUtils.AsNonNullVisual doesn't throw argument null exception when scrolling TreeView [142874]
Virtualizing TreeView doesn't cause it to scroll to random positions when collapsed and expanded [142912]
Fixed null reference exception from DataGridCellsPanel.HasCorrectRealizedColumns [143791]
Fixed a crash when deleting content from RichTextBox when a drawing tablet is installed [143800]
XamlReader.Save doesn't add extra text when using XmlWriterSettings.Indent [147082]
Printed characters not blurred if the printed XPS file uses transparent colors [147123]
All items are printed in XPS file using transparent colors [147125]
Added support for custom dictionaries in spell checking [142722]
Restored spell checking features on Windows 10 [142577]
Fixed a deadlock due to reentrancy in property changed handlers [145690]
Fixed ReadyToRun bugs that affected managed C++ and IL assemblies [145692]
Xmlns entries in XAML files withoug code behind don't cause usings to be added to the next XAML file compiled [145704]
Fixed the rendering of certain unicode characters on Windows 10 [145727]
Eliminated a delay in touch events [143839]
Improved touch performance when manipulating image [142488]
Fixed a null reference exception in GridViewHeaderRowPresenter when Columns is set to null during measure [142184]
WPF doesn't stop promoting touch to click after digitizer is removed and reconnected while touching the digitizer [142019]
Fixed TextBox argument exception when using some Chinese characters [141693]
Improved RichTextBox typing performance on low-end GPU [141828]
Chrome doesn't turn black on maximize on Windows 8.1 when GlassFrameThickness is -1 [124835]
Fixed a case where a button click event wasn't raised after deactivating the application's window [141633]
RichTextBox spellcheck corrections don't create double possessives [141660]
Data binding for elements in a Popup don't get lost [122280]
DatePicker DisplayDate binding works inside DataGrid, DataTemplate, and ControlTemplate [120278]
Using the Binding(string) constructor doesn't degrade performance [120967]
Fixed a memory leak in TreeView [105337]
Changing IsEnabled for a parent of a TextBlock affects its contents [91119]
Fixed an issue with partial trust applications running on a machine with a touch device [151160]
Fixed a bug caused by loading multiple Microsoft Visual Studio Tools for Office (VSTO) addins on touch enabled devices [142484]
Fixed a bug that caused Visual Studio to hang when saving a XAML file [110669]
WCF:
ServiceThrottle uses double-checked locking pattern for calls, sessions, and dynamic properties [96934]
MessageLogger.LogInternal doesn't call TraceXPathNavigator.ToString() [127642]
ProtocolException RoutingService to net.tcp doesn't reject all requests after end service recycles [142828]
Better performance on base64 strings with spaces [143785]
NetHttpBinding handles synchronous callback from WCF service correctly when called via WPF or WinForms app [145832]
Fixed a w3wp.exe crash when an exception occurs with WCF activity tracing enabled [145636]
Fixed a performance regression in selected large object variations [141815]
Binding including message credential over transport allows for messages where the To header is not signed [140756]
Fixed a null reference exception in System.Runtime.Serialization when ETW is enabled [105266]
Fixed IdentityModel.Claims to support multiple DNS entries [140718]
Workflow:
Sys.Tx APIs enable distributed transactions with a non-MSDTC coordinator [145813]
A user of EnlistPromotableSinglePhase can promote transactions to a non-MSDTC distributed transaction coordinator [145770, 142891, 142992]
System.Transaction allows for snapshot isolation for non-MSDTC promoter types [146607]
Sql implementation handles transient faults properly [113390]
Windows Forms:
CTRL+A works in multiline text boxes [145670]
Vertical scrollbar's Maximum is in sync with DataGridView's total height if the grid is populated while disabled [127329]
CancelButton or mnemonics respect Control.CausesValidation [144357]
Fixed a possible index out of range exception in ThreadContext when using custom MessageFilter [145665]
Fixed a null reference exception in System.Windows.Forms.ToolTip [145763]
Fixed the Categories name visibility in the Table/Columns Collection Editor when using high contrast scheme [145631]
Fixed several VisualStudio Designer Crashes [145639], [145710], [145652]
Fixed the size of the text for the Generating Previews dialog of the PrintPreviewControl from being cropped when scaling up to 500% in HDPI mode [145775]
Fixed the icons in the toolbox when scaling above 100% [145824]

[close]

http://msdn.microsoft.com/en-us/netframework/default.aspx

[SiLæncer]

Changelog

ASP.NET:

Improved support for localized error messages in data annotation validators:
Data annotation validators enable you to perform validation by adding one or more attributes to a class property. The attribute's ValidationAttribute.ErrorMessage element defines the text of the error message if validation fails. Starting with the .NET Framework 4.6.2, ASP.NET makes it easy to localize error messages.

Async support with session-state store providers:

ASP.NET now allows task-returning methods to be used with session-state store providers, thereby allowing ASP.NET apps to get the scalability benefits of async. To supports asynchronous operations with session state store providers, ASP.NET includes a new interface, System.Web.SessionState.ISessionStateModule, which inherits from IHttpModule and allows developers to implement their own session-state module and async session store providers. In addition, the SessionStateUtility class includes two new methods, IsSessionStateReadOnly and IsSessionStateRequired, that can be used to support asynchronous operations.
Async support for output-cache providers:

Starting with the .NET Framework 4.6.2, task-returning methods can be used with output-cache providers to provide the scalability benefits of async. Providers that implement these methods reduce thread-blocking on a web server and improve the scalability of an ASP.NET service. The following APIs have been added to support asynchronous output-cache providers:

The System.Web.Caching.OutputCacheProviderAsync class, which inherits from System.Web.Caching.OutputCacheProvider and allows developers to implement an asynchronous output-cache provider.
The OutputCacheUtility class, which provides helper methods for configuring the output cache.
18 new methods in the System.Web.HttpCachePolicyclass. These include GetCacheability, GetCacheExtensions, GetETag, GetETagFromFileDependencies, GetMaxAge, GetMaxAge, GetNoStore, GetNoTransforms, GetOmitVaryStar, GetProxyMaxAge, GetRevalidation, GetUtcLastModified, GetVaryByCustom, HasSlidingExpiration, and IsValidUntilExpires.
2 new methods in the System.Web.HttpCacheVaryByContentEncodings class: GetContentEncodings and SetContentEncodings.
2 new methods in the System.Web.HttpCacheVaryByHeaders class: GetHeaders and SetHeaders.
2 new methods in the System.Web.HttpCacheVaryByParams class: GetParams and SetParams.
In the System.Web.Caching.AggregateCacheDependency class, the GetFileDependencies method.
In the CacheDependency, the GetFileDependencies method.

CHARACTER CATEGORIES:

Characters in the .NET Framework 4.6.2 are classified based on the Unicode Standard, Version 8.0.0. In .NET Framework 4.6 and .NET Framework 4.6.1, characters were classified based on Unicode 6.3 character categories.
Support for Unicode 8.0 is limited to the classification of characters by the CharUnicodeInfo class and to types and methods that rely on it. These include the StringInfo class, the overloaded Char.GetUnicodeCategory method, and the character classes recognized by the .NET Framework regular expression engine. Character and string comparison and sorting is unaffected by this change and continues to rely on the underlying operating system or, on Windows 7 systems, on character data provided by the .NET Framework.

CRYPTOGRAPHY:

Support for X509 certificates containing FIPS 186-3 DSA:

The .NET Framework 4.6.2 adds support for DSA (Digital Signature Algorithm) X509 certificates whose keys exceed the FIPS 186-2 1024-bit limit.
In addition to supporting the larger key sizes of FIPS 186-3, the .NET Framework 4.6.2 allows computing signatures with the SHA-2 family of hash algorithms (SHA256, SHA384, and SHA512). FIPS 186-3 support is provided by the new System.Security.Cryptography.DSACng class.
In keeping with recent changes to the RSA class in the .NET Framework 4.6 and the ECDsa class in the .NET Framework 4.6.1, the DSA abstract base class in .NET Framework 4.6.2 has additional methods to allow callers to use this functionality without casting.

Increased clarity for inputs to ECDiffieHellman key derivation routines:

The .NET Framework 3.5 added support for Ellipic Curve Diffie-Hellman Key Agreement with three different Key Derivation Function (KDF) routines. The inputs to the routines, and the routines themselves, were configured via properties on the ECDiffieHellmanCng object. But since not every routine read every input property, there was ample room for confusion on the past of the developer.
To address this in the .NET Framework 4.6.2, the following three methods have been added to the ECDiffieHellman base class to more clearly represent these KDF routines and their inputs: DeriveKeyFromHash(ECDiffieHellmanPublicKey, HashAlgorithmName, Byte[], Byte[]), DeriveKeyFromHmac(ECDiffieHellmanPublicKey, HashAlgorithmName, Byte[], Byte[], Byte[]), DeriveKeyTls(ECDiffieHellmanPublicKey, Byte[], Byte[])

Support for persisted-key symmetric encryption:

The Windows cryptography library (CNG) added support for storing persisted symmetric keys and using hardware-stored symmetric keys, and the .NET Framework 4.6.2 mades it possible for developers to make use of this feature. Since the notion of key names and key providers is implementation-specific, using this feature requires utilizing the constructor of the concrete implementation types instead of the preferred factory approach (such as calling Aes.Create). Persisted-key symmetric encryption support exists for the AES (AesCng) and 3DES (TripleDESCng) algorithms.

SignedXml support for SHA-2 hashing:

The .NET Framework 4.6.2 adds support to the SignedXml class for RSA-SHA256, RSA-SHA384, and RSA-SHA512 PKCS#1 signature methods, and SHA256, SHA384, and SHA512 reference digest algorithms. The URI constants are all exposed on SignedXml. Any programs that have registered a custom SignatureDescription handler into CryptoConfig to add support for these algorithms will continue to function as they did in the past, but since there are now platform defaults, the CryptoConfig registration is no longer necessary.

SQLCLIENT:

Connection pooling and timeouts with Azure SQL databases:

When connection pooling is enabled and a timeout or other login error occurs, an exception is cached, and the cached exception is thrown on any subsequent connection attempt for the next 5 seconds to 1 minute. For more details, see SQL Server Connection Pooling (ADO.NET).
This behavior is not desirable when connecting to Azure SQL Databases, since connection attempts can fail with transient errors that are typically recovered quickly. To better optimize the connection retry experience, the connection pool blocking period behavior is removed when connections to Azure SQL Databases fail.
The addition of the new PoolBlockingPeriod keyword lets you to select the blocking period best suited for your app.

Enhancements for Always Encrypted:

To improve performance of parameterized queries against encrypted database columns, encryption metadata for query parameters is now cached. With the SqlConnection.ColumnEncryptionQueryMetadataCacheEnabled property set to true (which is the default value), if the same query is called multiple times, the client retrieves parameter metadata from the server only once
Column encryption key entries in the key cache are now evicted after a configurable time interval, set using the SqlConnection.ColumnEncryptionKeyCacheTtl property

WINDOWS COMMUNICATION FOUNDATION:

WCF transport security support for certificates stored using CNG:

WCF transport security supports certificates stored using the Windows cryptography library (CNG). In the .NET Framework 4.6.2, this support is limited to using certificates with a public key that has an exponent no more than 32 bits in length. When an application targets the .NET Framework 4.6.2, this feature is on by default.
For applications that target the .NET Framework 4.6.1 and earlier but are running on the .NET Framework 4.6.2, this feature can be enabled by adding the following line to the section of the app.config or web.config file.
Better support for multiple daylight saving time adjustment rules by the DataContractJsonSerializer class:
Customers can use an application configuration setting to determine whether the DataContractJsonSerializer class supports multiple adjustment rules for a single time zone. This is an opt-in feature. To enable it, add the following setting to your app.config file.
When this feature is enabled, a DataContractJsonSerializer object uses the TimeZoneInfo type instead of the TimeZone type to deserialize date and time data. TimeZoneInfo supports multiple adjustment rules, which makes it possible to work with historic time zone data; TimeZone does not.
Support for preserving a UTC time when serializing and deserializing with the XMLSerializer class:
Ordinarily, when the XmlSerializer class is used to serialize a UTC DateTime value, it creates a serialized time string that preserves the date and time but assumes the time is local. For example, if you instantiate a UTC date and time by calling the following code.

NetNamedPipeBinding best match:

WCF has a new app setting that can be set on client applications to ensure they always connect to the service listening on the URI that best matches the one that they request. With this app setting set to false (the default), it is possible for clients using NetNamedPipeBinding to attempt to connect to a service listening on a URI that is a substring of the requested URI.
For example, a client tries to connect to a service listening at net.pipe://localhost/Service1, but a different service on that machine running with administrator privilege is listening at net.pipe://localhost. With this app setting set to false, the client would attempt to connect to the wrong service. After setting the app setting to true, the client will always connect to the best matching service.

SSL 3.0 is not a default protocol:

When using NetTcp with transport security and a credential type of certificate, SSL 3.0 is no longer a default protocol used for negotiating a secure connection. In most cases, there should be no impact to existing apps, because TLS 1.0 is included in the protocol list for NetTcp. All existing clients should be able to negotiate a connection using at least TLS 1.0. If Ssl3 is required, use one of the following configuration mechanisms to add it to the list of negotiated protocols.
The SslStreamSecurityBindingElement.SslProtocols property
The TcpTransportSecurity.SslProtocols property
The section of the section
The section of the section

WINDOWS PRESENTATION FOUNDATION:

Group sorting:

An application that uses a CollectionView object to group data can now explicitly declare how to sort the groups. Explicit sorting addresses the problem of non-intuitive ordering that occurs when an app dynamically adds or removes groups, or when it changes the value of item properties involved in grouping. It can also improve the performance of the group creation process by moving comparisons of the grouping properties from the sort of the full collection to the sort of the groups.
To support group sorting, the new GroupDescription.SortDescriptions and GroupDescription.CustomSort properties describe how to sort the collection of groups produced by the GroupDescription object. This is analogous to the way the identically named ListCollectionView properties describe how to sort the data items.
Two new static properties of the PropertyGroupDescription class, CompareNameAscending and CompareNameDescending, can be used for the most common cases.
For example, the following XAML groups data by age, sort the age groups in ascending order, and group the items within each age group by last name.

Soft keyboard support:

Soft Keyboard support enables focus tracking in a WPF applications by automatically invoking and dismissing the new Soft Keyboard in Windows 10 when the touch input is received by a control that can take textual input.
In previous versions of the .NET Framework, WPF applications cannot opt into the focus tracking without disabling WPF pen/touch gesture support. As a result, WPF applications must choose between full WPF touch support or rely on Windows mouse promotion

Per-monitor DPI:

To support the recent proliferation of high-DPI and hybrid-DPI environments for WPF apps, WPF in the .NET Framework 4.6.2 enables per-monitor awareness. See the samples and developer guide on GitHub for more information about how to enable your WPF app to become per-monitor DPI aware.
In previous versions of the .NET Framework, WPF apps are system-DPI aware. In other words, the application's UI is scaled by the OS as appropriate, depending on the DPI of the monitor on which the app is rendered. ,
For apps running under the .NET Framework 4.6.2, you can disable per-monitor DPI changes in WPF apps by adding a configuration statement to the section of your application configuration file.

WINDOWS WORKFLOW FOUNDATION:

Support for C# expressions and IntelliSense in the Re-hosted WF Designer
Starting with the .NET Framework 4.5, WF supports C# expressions in both the Visual Studio Designer and in code workflows. The Re-hosted Workflow Designer is a key feature of WF that allows for the Workflow Designer to be in an application outside Visual Studio (for example, in WPF). Windows Workflow Foundation provides the ability to support C# expressions and IntelliSense in the Re-hosted Workflow Designer.

Availability of IntelliSense when a customer rebuilds a workflow project from Visual Studio:

In versions of the .NET Framework prior to the .NET Framework 4.6.2, WF Designer IntelliSense is broken when a customer rebuilds a workflow project from Visual Studio. While the project build is successful, the workflow types are not found on the designer, and warnings from IntelliSense for the missing workflow types appear in the Error List window. The .NET Framework 4.6.2 addresses this issue and makes IntelliSense available.

Workflow V1 applications with Workflow Tracking on now run under FIPS-mode:

Machines with FIPS Compliance Mode enabled can now successfully run a workflow Version 1-style application with Workflow tracking on. To enable this scenario, you must make the following change to your app.config file: 'add key="microsoft:WorkflowRuntime:FIPSRequired" value="true" /'

Workflow Improvements when using Dynamic Update with Visual Studio Workflow Designer:

The Workflow Designer, FlowChart Activity Designer, and other Workflow Activity Designers now successfully load and display workflows that have been saved after calling the DynamicUpdateServices.PrepareForUpdate method. In versions of the .NET Framework before the .NET Framework 4.6.2, loading a XAML file in Visual Studio for a workflow that has been saved after calling DynamicUpdateServices.PrepareForUpdate can result in the following issues:

The Workflow Designer can't load the XAML file correctly (when the ViewStateData.Id is at the end of the line).
Flowchart Activity Designer or other Workflow Activity Designers may display all objects in their default locations as opposed to attached property values.

CLICKONCE:

ClickOnce has been updated to support TLS 1.1 and TLS 1.2 in addition to the 1.0 protocol, which it already supports. ClickOnce automatically detects which protocol is required; no extra steps within the ClickOnce application are required to enable TLS 1.1 and 1.2 support.

CONVERTING WINDOWS FORMS AND WPF APPS TO UWP APPS:

Windows now offers capabilities to bring existing Windows desktop apps, including WPF and Windows Forms apps, to the Universal Windows Platform (UWP). This technology acts as a bridge by enabling you to gradually migrate your existing code base to UWP, thereby bringing your app to all Windows 10 devices.
Converted desktop apps gain an app identity similar to the app identity of UWP apps, which makes UWP APIs accessible to enable features such as Live Tiles and notifications. The app continues to behave as before and runs as a full trust app. Once the app is converted, an app container process can be added to the existing full trust process to add an adaptive user interface. When all functionality is moved to the app container process, the full trust process can be removed and the new UWP app can be made available to all Windows 10 devices.

DEBUGGING IMPROVEMENTS:

The unmanaged debugging API has been enhanced in the .NET Framework 4.6.2 to perform additional analysis when a NullReferenceException is thrown so that it is possible to determine which variable in a single line of source code is null. To support this scenario, the following APIs have been added to the unmanaged debugging API.
The ICorDebugCode4, ICorDebugVariableHome, and ICorDebugVariableHomeEnum interfaces, which expose the native homes of managed variables. This enables debuggers to do some code flow analysis when a NullReferenceException occurs and to work backwards to determine the managed variable that corresponds to the native location that was null.
The ICorDebugType2::GetTypeID method provides a mapping for ICorDebugType to COR_TYPEID, which allows the debugger to obtain a COR_TYPEID without an instance of the ICorDebugType. Existing APIs on COR_TYPEID can then be used to determine the class layout of the type.

[close]

http://msdn.microsoft.com/en-us/netframework/default.aspx

[SiLæncer]

ASoft .NET Version Detector is a lightweight tool that gives information on the different versions of Microsoft .NET that are installed on a machine. If a certain version isn't on the machine, you can simply follow the link that .NET Version Detector suggests, so it is easier for the novice user to find the runtimes. Detailed information is given of where the .NET Frameworks are installed with links to the directories. The details can easily be copied by a user, to paste in a mail.

Freeware

http://www.asoft.be/prod_netver.html

[SiLæncer]

Changelog

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.

[close]

http://msdn.microsoft.com/en-us/netframework/default.aspx

[SiLæncer]

Release Notes : https://docs.microsoft.com/en-us/dotnet/framework/whats-new/index#v471

http://msdn.microsoft.com/en-us/netframework/default.aspx

[SiLæncer]

The Microsoft .NET Framework Repair Tool detects and repairs frequently occurring issues that affect the Microsoft .NET Framework setup or updates.

The tool tries to resolve those issues by applying known fixes or by repairing the corrupted installations of the supported .NET Framework versions. The tool has an easy-to-use wizard-based user interface (UI). It also supports command line usage together with more advance options.

Freeware

http://www.microsoft.com/en-us/download/details.aspx?id=30135

[SiLæncer]

Release Notes : https://docs.microsoft.com/en-us/dotnet/framework/whats-new/index#v472

http://msdn.microsoft.com/en-us/netframework/default.aspx

[SiLæncer]

Whats new:>>

Add the ability to verify the .NET Framework 4.7.2.

https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-guide/

[SiLæncer]

Whats new:>>

Added support for cleaning up the .NET Framework 4.7.2.

http://blogs.msdn.com/b/astebner/

[SiLæncer]

Infos zu dieser Version -> https://docs.microsoft.com/en-us/dotnet/framework/whats-new/index

http://msdn.microsoft.com/en-us/netframework/default.aspx

[SiLæncer]

Changelog

    What’s new in .NET 5:

    NET 5.0 is the next major release of .NET Core following 3.1. We named this new release .NET 5.0 instead of .NET Core 4.0 for two reasons:

    We skipped version numbers 4.x to avoid confusion with .NET Framework 4.x.
    We dropped “Core” from the name to emphasize that this is the main implementation of .NET going forward. .NET 5.0 supports more types of apps and more platforms than .NET Core or .NET Framework.
    ASP.NET Core 5.0 is based on .NET 5.0 but retains the name “Core” to avoid confusing it with ASP.NET MVC 5. Likewise, Entity Framework Core 5.0 retains the name “Core” to avoid confusing it with Entity Framework 5 and 6.

    .NET 5.0 includes the following improvements and new features compared to .NET Core 3.1:

    C# updates
    F# updates
    Visual Basic updates
    System.Text.Json new features
    Single file apps
    App trimming
    Windows ARM64 and ARM64 intrinsics
    Tooling support for dump debugging
    The runtime libraries are 80% annotated for nullable reference types

    Performance improvements:

    Garbage Collection (GC)
    System.Text.Json
    System.Text.RegularExpressions
    Async ValueTask pooling
    Container size optimizations
    Many more areas
    NET 5.0 doesn’t replace .NET Framework
    .NET 5.0 is the main implementation of .NET going forward and .NET Framework 4.x is still supported.
    NET 5.0 doesn’t replace .NET Standard
    New application development can specify the net5.0 target framework moniker (TFM) for all project types, including class libraries. Sharing code between .NET 5 workloads is simplified in that all you need is the net5.0 TFM.
    For .NET 5.0 apps and libraries, the net5.0 Target Framework Moniker (TFM) combines and replaces the netcoreapp and netstandard TFMs. However, if you plan to share code between .NET Framework, .NET Core, and .NET 5 workloads, you can do so by specifying netstandard2.0 as your TFM. For more information, see .NET Standard.

[close]

http://msdn.microsoft.com/en-us/netframework/default.aspx

[SiLæncer]

Infos zu dieser Version -> https://docs.microsoft.com/en-us/dotnet/framework/whats-new/#v481

http://msdn.microsoft.com/en-us/netframework/default.aspx

[SiLæncer]

Infos zu dieser Version -> https://github.com/dotnet/core/blob/main/release-notes/7.0/7.0.5/7.0.5.md

http://msdn.microsoft.com/en-us/netframework/default.aspx

[SiLæncer]

Infos zu dieser Version -> https://github.com/dotnet/core/blob/main/release-notes/7.0/7.0.10/7.0.10.md

http://msdn.microsoft.com/en-us/netframework/default.aspx