Blazor on the Server is coming with .NET Core Version 3.0 in the second half of 2019. Here's what Peter thinks of that (and he's not completely happy).
When it comes to retrieving the object sent to you by a Web Service, there's an easy way to do it and a hard way to do it. The problem is that the easy way is hard to get.
Visual Studio Code now does Blazor development thanks to updated Razor tooling support in a popular C# extension for the code editor.
On the same day we reported "the end of the experiment is in sight" for Microsoft's Blazor project, it did indeed graduate from experimental status to a preview of a new way to do Web UI with .NET languages like C#.
.NET Core provides a framework that logging systems can be snapped into. However, what's most important about this framework is how you write your messages out. It's the quality of the message that will let you find where your problems are.
Daniel Roth and Steve Sanderson of Microsoft's Blazor development team provided an update on the long-awaited, experimental project that boosts .NET development for the Web, stating "the end of the experiment is in sight."
Blazor, like most systems for generating Web pages, supports using layout pages for repeated content. Here's what works, what doesn't (yet) work and work-arounds I've discovered for what doesn't work.
TypeScript 3.4 is out with the usual array of new features, of which a new --incremental flag can lead to faster project builds after the first such build
RedMonk's lastet programming language popularity report singles out TypeScript as a big mover among an otherwise fairly static ranking of the usual leaders.