I wrote this post to make as many developers and sysadmins aware of the (very critical) bug in .Net 4.6 as possible. Please take a minute to read and make anyone deploying (or thinking about deploying) .Net 4.6 aware of the issue. If you have any questions, I'm happy to answer here, on the blog, or on reddit.
5 comments
[ 3.8 ms ] story [ 21.9 ms ] threadI've put a full stop on upgrading our test kit to this while we analyse everything.