3 ms·

Update summary (some smaller fixes/improvements omitted): - Allow paths that are greater than 260 character (MAX_PATH). - Enable extended path syntax a

by NKCSS 10y ago

Update summary (some smaller fixes/improvements omitted): - Allow paths that are greater than 260 character (MAX_PATH). - Enable extended path syntax and file namespaces (\\?\, \\.\). - X509 Certificates Now Support FIPS 186-3 Digital Signature Algorithm (Keys > 1024 bits) - SignedXml Support for SHA-2 Hashing - Groundwork for more informative NullRefrence Exceptions - ClickOnce TLS 1.1, 1.2 and client certificate support - ASP.NET DataAnnotation Localization - System.Data.SqlClient Always Encrypted Modus - WCF removed support for SSL 3 - Per monitor DPI support for WPF - Show/Hide soft keyboard from WPF code Minor nitpick, but why would you name your XML example files .cs (C#) files :P https://gist.githubusercontent.com/staceyhaffner/8bad9c0895b647703784db65237c5b5f/raw/7384c36d9cd668bc6988d4da6c4fce28737d2616/longpathsample1.cs https://gist.githubusercontent.com/staceyhaffner/8bad9c0895b...

jsingleton 10y ago
More background on the long paths: https://blogs.msdn.microsoft.com/jeremykuhne https://blogs.msdn.microsoft.com/jeremykuhne There's some nice small Async enhancements in this patch too, such as improvements to Output Caching (which isn't available in ASP.NET Core, although Response Caching to set headers for proxies is). It's good to see MS are still updating .NET Framework as I think .NET Core needs a bit more time before it's suitable for enterprise style applications. Patches are coming soon though: https://blogs.msdn.microsoft.com/dotnet/2016/07/15/net-core-roadmap https://blogs.msdn.microsoft.com/dotnet/2016/07/15/net-core-... edit: More info on Response Caching: https://docs.asp.net/en/latest/performance/caching/response.html https://docs.asp.net/en/latest/performance/caching/response.... Shameless plug: I've written about Response Caching in my book on ASP.NET Core (https://unop.uk/book https://unop.uk/book).
rbanffy 10y ago
> - Allow paths that are greater than 260 character (MAX_PATH). That's surprising.

by NKCSS 10y ago

jsingleton 10y ago

More background on the long paths: https://blogs.msdn.microsoft.com/jeremykuhne https://blogs.msdn.microsoft.com/jeremykuhne There's some nice small Async enhancements in this patch too, such as improvements to Output Caching (which isn't available in ASP.NET Core, although Response Caching to set headers for proxies is). It's good to see MS are still updating .NET Framework as I think .NET Core needs a bit more time before it's suitable for enterprise style applications. Patches are coming soon though: https://blogs.msdn.microsoft.com/dotnet/2016/07/15/net-core-roadmap https://blogs.msdn.microsoft.com/dotnet/2016/07/15/net-core-... edit: More info on Response Caching: https://docs.asp.net/en/latest/performance/caching/response.html https://docs.asp.net/en/latest/performance/caching/response.... Shameless plug: I've written about Response Caching in my book on ASP.NET Core (https://unop.uk/book https://unop.uk/book).

rbanffy 10y ago

> - Allow paths that are greater than 260 character (MAX_PATH). That's surprising.