Digests » 138
This time last year we did a Microsoft Virtual Academy class on what was then called "ASP.NET 5." It made sense to call it 5 since 5 > 4.6, right? But since then ASP.NET 5 has become .NET Core 1.0 and ASP.NET Core 1.0. It's 1.0 because it's smaller, newer, and different. As the .NET "full" framework marches on, on Windows, .NET Core is cross-platform and for the cloud.
Over the last few months there have been several blog posts looking at GC pauses in different programming languages or runtimes. It all started with a post looking at the latency of the Haskell GC, next came a follow-up that compared Haskell, OCaml and Racket, followed by Go GC in Theory and Practice, before a final post looking at the situation in Erlang.
NET Core is great. It is one of the best products of Microsoft’s shift to a more open source, cross platform company and whilst still limited in comparison to the traditional .NET framework there are still plenty of avenues for powerful development using C# or F# thanks to libraries such as ASP.Net Core and Entity Framework Core.
In my last blog post I discussed Tuple Types and how, in my opinion, they make scenario's such as returning multiple values from a method a lot easier than some of the previous alternatives. In this post I'd like to introduce you to another new feature of C# 7.0 that goes hand in hand with Tuples, Deconstruction.
At the beginning of each new year, many people take on a challenge to learn something new or commit to reinforcing existing skills. Over the next two blog posts, we will guide you through two amazing, free, developer training video series: C# fundamentals and UWP Development.