Our WPF SyntaxEditor vNext beta began a week ago and has been going well. As we prepare for a 2019.1 version release, we are looking at making some other moves and wanted to get your feedback on them. First, let’s dig into some low-level .NET details to set up the background.
About .NET Core 3.0
.NET Core 3.0 is a newer, cross-platform, open source variation containing much of what is in the .NET Framework. It is still in preview with release date later this year, but is already much faster and more light-weight. Microsoft has been ensuring that it is capable of supporting Windows desktop development platforms like WPF and WinForms, and they have been updating Visual Studio to support desktop app development based on .NET Core 3.0. It also allows you to introduce newer Windows 10 APIs in desktop apps and host XAML islands (UWP controls). Further, .NET Framework 4.8 is intended to be the final version of that framework, with .NET Core as the migration path moving forward. More news in this area is sure to come in this week’s Build 2019 conference.
Moving to .NET Core 3.0
We’ve had numerous customers ask about moving our WPF Controls to .NET Core 3.0. A near-term goal for us is to ship native .NET Core 3.0 variations of our WPF Control assemblies as option, while still shipping .NET Framework-based variations.
On a side note, the existing WPF Control assemblies can already be used within .NET Core 3.0 applications. They are based on .NET Framework-only but are portable, and will work in .NET Core 3.0 applications.
What is .NET Standard?
This is where things get a bit more complex. .NET Framework is the base set of .NET APIs we have been using ever since .NET began. .NET Standard was more recently created as an API contract of sorts where a framework that implements a certain .NET Standard version guarantees that it supports a certain set of .NET APIs.
Think of .NET Standard like a set of interfaces and .NET Framework like a set of classes that implement those interfaces. Thus, more recent .NET Framework versions implement .NET Standard.
.NET Core is simply another implementation of .NET Standard. Since the API implementation surface area is now about the same between .NET Core and .NET Framework, it’s a good time to consider moving to .NET Core for future work.
.NET Framework 4.6.1
The 4.6.1 version of the .NET Framework is now mature, as it was released at the end of 2015 and requires Visual Studio 2015 or later for development. It supports .NET Standard 2.0.
Back on Framework Updates
Both .NET Core 3.0 and .NET Framework 4.6.1 implement .NET Standard 2.0, which is the minimum set of APIs a number of our WPF Controls and SyntaxEditor text/parsing assemblies require.
One option we’ve been considering is:
- Moving some of our non-UI class libraries like the various SyntaxEditor text assemblies that have no WPF references to be .NET Standard 2.0 class libraries. This would enable them to work in .NET Framework, .NET Core, Mono, etc… basically any framework implementing .NET Standard 2.0.
- Continuing to ship .NET Framework versions of the WPF Control assemblies, but making their minimum target .NET 4.6.1, compared to the current .NET 4.0 minimum target. The .NET 4.6.1 version is needed to support references to .NET Standard 2.0 assemblies mentioned in the previous bullet, and would require you to target .NET 4.6.1 or later in your .NET Framework-based applications.
- Adding .NET Core 3.0 versions of the WPF Control assemblies, so there is zero .NET Framework dependency for customers who wish to go purely to .NET Core 3.0.
A Twitter Poll
Please answer our Twitter poll as to whether you would support the changes mentioned above or not. If not, please indicate in the comments below or in the Twitter poll why.
WPF SyntaxEditor vNext Beta
And as we close out this blog post, if any other WPF Controls customers would like to participate in the WPF SyntaxEditor vNext beta, please contact our support team.