Note: I was away last week, hence no roundup. This week is a bit of catch up.Follow @codeopinion
Roslyn is the codename-that-stuck for the open-source compiler for C# and Visual Basic.NET. Here’s how it started in the deepest darkness of last decade’s corporate Microsoft, and became an open source, cross-platform, public language engine for all things C# (and VB, which I’ll take as a given for the rest of this piece).
Really interesting read about the history and how it all came together. I love reading these historical accounts.
In May, we announced .NET Core 3.0, the next major version of .NET Core that adds support for building desktop applications using WinForms, WPF, and Entity Framework 6. We also announced some exciting updates to .NET Framework which enable you to use the new modern controls from UWP in existing WinForms and WPF applications.
I think this is in a way trying to frame that .NET Framework isn’t dead, although I still feel differently. Innovation is happening in .NET Core. It’s ultimately the future even if .NET Framework will always be supported.
IMiddlewareinterface is an extensibility point for middleware activation. It defines middleware for application’s request pipeline like the Conventional Middleware where
InvokeAsync()handles the requests and returns a
Taskthat represents the execution of the middleware.
Why have I never seen/heard IMiddleware before? Have you?
Warp lets you create self-contained single binary applications making it simpler and more ergonomic to deliver your application to your customers. A self-contained binary is specially convenient when the technology you use, such as .NET Core, Java and others, contain many dependencies that must be shipped alongside your application.
Warp is written in Rust and is supported on Linux, Windows and macOS.
Pretty cool project for creating a single binary. Very different then CoreRT however.
DDD Isn’t Done. A Skeptical, Optimistic, Pragmatic Look. We have more experience now. We have better tools now. We have an architectural environment better suited to DDD than the typical 2003 architecture. Certainly, some people are getting a lot out of DDD — but not so very many. DDD has always been difficult, and it still is. And we might be held back by some dogmatic notions of what it should look like.