-
TwokaB
Blazor WebView control for WPF, Android, macOS, iOS. Run Blazor on .NET Core and Mono natively inside a Webview.
-
Roslyn
The Roslyn .NET compiler provides C# and Visual Basic languages with rich code analysis APIs.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
MobileBlazorBindings
Experimental Mobile Blazor Bindings - Build native and hybrid mobile apps with Blazor
-
ASP.NET Core
ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
Yes, basically (though "backend" isn't quite the right term here, I would say). You can see a preview of this at https://github.com/jspuij/TwokaB
Yeah, I wonder how this announcement plays into that. There's been a wiki page regarding limitations for a long time, and I wouldn't be surprised if the realization was that an entirely different approach to EnC was in order.
Yes, that is it. I found the source in the meantime: https://github.com/dotnet/MobileBlazorBindings/tree/master/samples/WpfBlazorSample/WpfBlazorSample
If you still don't believe that Standard is dead, look at when the latest version was announced: 2018-11-05, over two years ago. Since that time there have been three full releases of Core/5.0 (2.2, 3.1, 5.0) and the preview of 6.0. It's quite clear where Microsoft's priorities are. Or look at the most recent activity on the .NET Standard repo: 2020-05-22, over 10 months ago.
For what it's worth, Microsoft seems to be handling this like a bug and has merged a fix for .NET 5. Not sure if this has been released yet, or will actually resolve the issue, but it was referenced on the wkhtmltopdfrepo issues here
They have a tracking issue at github which makes me pretty excited on improvements of the inner dev loop.