Showing archive results for 2019

ML.NET is an open-source and cross-platform machine learning framework (Windows, Linux, macOS) for .NET developers. ML.NET offers Model Builder Model Builder (a simple UI tool for Visual Studio) and CLI to make it super easy to build custom ML Models using AutoML. Using ML.NET, developers can leverage their existing tools and skillsets to dev...

In part 1 of this blog series, I began the process of porting a sample WPF app to .NET Core. In that post, I described the .NET Core migration process as having four steps: We previously went through the first two steps - reviewing the app and its dependencies (including NuGet dependencies and a .NET Portability Analyzer report), updating NuGet ...

Olia recently wrote a post about how to port a WinForms app from .NET Framework to .NET Core. Today, I'd like to follow that up by walking through the steps to migrate a sample WPF app to .NET Core 3. Many of these steps will be familiar from Olia's post, but I've tried to differentiate this one by including some additional common dependencies that...

At the Build conference in May 2019, we mentioned that, after we add WinForms, WPF and Entity Framework 6 to .NET Core 3.0, we do not plan to add any more of the technologies from .NET Framework to .NET Core. This means we will not be adding ASP.NET Web Forms, WCF, Windows Workflow, .NET Remoting and/or the various other smaller APIs to .NET Cor...

We just shipped 1.1.0 Preview 1 of Azure SignalR Service SDK to support some new features in ASP.NET Core 3.0, including endpoint routing and server-side Blazor. Let's take a look how you can use them in your Azure SignalR application. Here is the list of what's new in this release: Endpoint routing support for ASP.NET Core 3 For thos...

Since I've been working with the community on porting desktop applications from .NET Framework to .NET Core, I've noticed that there are two camps of folks: some want a very simple and short list of instructions to get their apps ported to .NET Core while others prefer a more principled approach with more background information. Instead of writing ...

TL;DR We've moved the F# GitHub repository from microsoft/visualfsharp to dotnet/fsharp, as specified in the corresponding RFC. F# has a somewhat strange history in its name and brand. If we roll back the clocks to the year 2015, F# sort of had two identities. One side of this was Visual F#, or "VisualFSharp"; a product within Visual Studio ...

Try .NET is an interactive documentation generator for .NET Core. Using the dotnet try global tool you can now create interactive documentation too. This is an early preview of the dotnet try global tool so, please check our repository and NuGet package for regular updates.

Take a tour through some of the many improvements, big and small, that have gone into the .NET Core 3.0 runtime and core libraries to make apps and services leaner and faster.

Default implementations in interfaces With last week's posts Announcing .NET Core 3.0 Preview 5 and Visual Studio 2019 version 16.1 Preview 3, the last major feature of C# 8.0 is now available in preview. A big impediment to software evolution has been the fact that you couldn't add new members to a public interface. You would break existing im...