.NET Framework October 2018 Security and Quality Rollup

Today, we released the October 2018 Security and Quality Rollup. Security No new security fixes. See .NET Framework September 2018 Security and Quality Rollup for the latest security update. Quality and Reliability This release contains the following quality and reliability improvements. CLR Updated code to prevent errors regarding invalid date format when Japanese Era 4 is used with a future date [568291] Parsing Japanese dates having a year number exceeding the number of years in that date era will succeed instead of throwing errors [603100] When asynchronously reading a process output an IndexOutOfRangeException is thrown when less than a character's worth of bytes is read at the beginning of a line [621951] Fix in the JIT compiler for a rare case of struct field assignments, described here: https://github.com/Microsoft/dotnet/issues/779 [641182] DateTime.Now and DateTime.Utc will now always be synchronized with the system time, DateTime and DateTimeOffset operations will continue to work as it used to work [645660] Spin-waits in several synchronization primitives were conditionally improved to perform better on Intel Skylake and more recent microarchitectures.

✔ Read More...

I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.