.NET Blog
Free. Cross-platform. Open source. A developer platform for building all your apps.
Latest posts
Migrating a Sample WPF App to .NET Core 3 (Part 2)
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 package references, and migrating the project file. In this post, we'll complete the migration by making the necessary code changes to get the app building and running against .NET Core 3. Step 3: Fix build issues The third step of the porting process is getting the p...
Migrating a Sample WPF App to .NET Core 3 (Part 1)
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 users are likely to run into like WCF client usage or third-party UI packages. To keep this post from being too long, I will split it into two parts. In this first part, we'll prepare for migration and create a new csproj file for the .NET Core version of the app. I...
Supporting the community with WF and WCF OSS projects
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 Core. For new applications, there are better technologies that serve a similar purpose and provide more capabilities or better experiences. We think of .NET Core as the framework our customers will build brand new applications or port applications that they are still spend...
What’s new in Azure SignalR 1.1.0 Preview 1
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 those who are using Azure SignalR, you should be familiar with and . These two methods are required if you want to switch your app server from self-hosted SignalR to use Azure SignalR. A typical Azure SignalR application usually looks like this in Startup.cs (note where ...
Porting desktop apps to .NET Core
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 up a "Swiss Army knife"-document, we are going to publish two blog posts, one for each camp: If you prefer watching videos instead of reading, here is the video where I do everything that is described below. Step 0 - Prerequisites To port your desktop...
The F# development home on GitHub is now dotnet/fsharp
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 comprised of a compiler and tooling that you could use on Windows. The other side was F#, or "FSharp"; an independent language with a roaring community that built F# tools, a library ecosystem, and multiple packagings of F# independently of Microsoft. Although this d...
Create Interactive .NET Documentation with Try .NET
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.
Performance Improvements in .NET Core 3.0
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
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 implementers of the interface; after all they would have no implementation for the new member! Default implementations help with that. An interface member can now be specified with a code body, and if an implementing class or struct does not provide an implementation o...