{"id":5174,"date":"2016-02-11T16:55:05","date_gmt":"2016-02-11T16:55:05","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/dotnet\/?p=5174"},"modified":"2021-09-30T12:17:55","modified_gmt":"2021-09-30T19:17:55","slug":"the-week-in-net-2112016","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/the-week-in-net-2112016\/","title":{"rendered":"The week in .NET – 2\/11\/2016"},"content":{"rendered":"

This issue of the Week in .NET is slightly late, and I apologize for that. I was visiting some customers in California for the first half of the week, and they’ve kept me very busy. I’m writing this post on the plane to Seattle. While I was in LA, I also visited the LADOTNET user group, where I talked about .NET Core, C# 6, and the future of C#<\/a>. You can find links to my slides in the .NET section below.<\/p>\n

To read last week’s post, see The week in .NET \u2013 2\/2\/2016<\/a>.<\/p>\n

<\/a>On.NET<\/a><\/h2>\n

Last week on On .NET, we had Scott Hunter<\/a>, who is the new director of Program Management for .NET, in other words my grand-boss.<\/p>\n

We’ll be live on Friday 10AM Pacific Time<\/a>, instead of our usual Thursday time. I’m happy to announce that our guest for this week is Aaron Stannard. We’ll talk about Akka.NET<\/a>, the actor framework for .NET, and about Aaron’s other projects NBench<\/a> and DotNetty<\/a>.<\/p>\n

<\/a>Package of the week: Polly<\/h2>\n

In a world of increasingly distributed applications, exception handling is not always the most convenient way of handling transient errors and the flow associated with them. For instance, if you’re communicating with a distant service, you may want to implement a retry policy in case it fails. Polly<\/a> provides a fluent API that easily expresses such policies.<\/p>\n