Quo Vadis, MSMQ and .NET Core?

“Microsoft Message Queuing (MSMQ) is currently not available for .NET Core. While other message queuing systems are generally preferred, many enterprise applications were based on MSMQ and this creates a problem for teams looking to migrate from .NET Framework to .NET Core or the upcoming .NET 5. But a recent pull request for Reference Source may change the situation.”

By Jonathan Allen

Source: MSMQ and .NET Core

.NET 5 – One .NET to rule them all

There is No More .NET Core, it’s .NET 5

Here’s the umbrella of .NET 5 to the rescue. It’s a MAJOR change because of the following reasons:

As the first part of this unification scheme, Microsoft’s Xamarin mobile development platform will switch from using the Mono BCL to join other components leveraging the .NET Core BCL. With that move, Xamarin mobile development will be folded into .NET 5. That means that for the first time, one BCL-based framework will handle all app models:

  • ASP.NET Core
  • Entity Framework Core
  • Blazor
  • WinForms
  • WPF
  • Xamarin
  • ML.NET

Wait, WPF and WinForms made it into .NET 5? Yes, it’s true. Hello there, old friends! Nice to see them included in this runtime. The idea of using one SDK to build apps with is pretty exciting stuff, if you ask me.

Source: The Most Exciting Promise of .NET 5 | Okta Developer

How to port desktop applications to .NET Core 3.0 | On .NET | Channel 9

“With every subsequent release, .NET Core continues to improve with greater levels performance, security and new features that help enhance developer workflow. In .NET Core 3.0, developers will see tons of improvements around our capabilities to build Cloud, Web, IoT, and Machine Learning applications. One of the biggest enhancements will also be support for Windows desktop applications (Windows only).”

Source: How to port desktop applications to .NET Core 3.0 | On .NET | Channel 9