In the fast-paced realm of modern software development, proficiency across a full stack of technologies is not just beneficial, it's essential. Microsoft has an entire stack of open source development components in its .NET platform (formerly known as .NET Core) that can be used to build an end-to-end set of applications.
Microsoft's Steve Sanderson, the creator of Blazor, introduced his latest pet project, Smart Components for easy AI-driven interfaces in .NET apps.
Microsoft shipped the first release candidates for its .NET 8 offerings, including the main framework, the .NET MAUI evolution of Xamarin.Forms and the ASP.NET Core web-dev components, not to mention Entity Framework (EF8) for data devs.
While .NET 8 Preview 5 includes the usual raft of new features and functionality around installers, binaries, container images an so on, much of the action in this cycle concerned ASP.NET Core and its Blazor tooling, which allows for coding web projects in C# instead of JavaScript while taking advantages of new component rendering advancements.
Microsoft recommends replacing relic from old .NET Framework with Blazor, but you can still do ASP.NET Web Forms apps in Visual Studio 2022 if you want to, with a couple tweaks.
Native ahead-of-time (AOT) compilation -- a much-requested and long-awaited feature for .NET -- is getting closer in the new .NET 7 Preview 2.
The new R3 2021 release of Progress Telerik developer tooling for .NET developers is out with new controls for Blazor, .NET MAUI (evolution of Xamarin.Forms) and desktop offerings including WinUI, WPF and WinForms.
Of course, ASP.NET isn't a programming language, and some question whether PHP even fits the bill.
Did you ever wonder why Microsoft doesn't provide a component library for Blazor, like Angular and others do?
Echoing an earlier report on the popularity of ASP.NET in the .NET/C# tech stack, a new survey from the .NET Foundation finds the web framework dominates the ranking of app models used by respondents.
A new development skills report from DevSkiller reveals the most popular components in the .NET/C# tech stack. Think web.
When you need to integrate authorization with procedural code, you're going to need your application's ClaimsPrincipal object so that you can check the user's authorization claims. Here's both how to get to the ClaimsPrincipal and how to extend it with custom claims.
When it comes to controlling which users can access which functionality in a Blazor application you not only have access to all of the user’s authentication you can authorize the user’s actions without writing any code.
Once you've got a contract that describes a gRPC service, creating the service itself and a client that can call the service is easy. In fact, Visual Studio will do most of the work for you ... once you've got your projects set up correctly, that is.
You can store encrypted values in your ASP.NET Core configuration file and seamlessly decrypt the values as you retrieve them. But there are, at least, two issues that you'll need to address.
You can create Blazor components by combining other Blazor components but you'll almost certainly need to share data between those components. Here are all the options currently open to you.
ASP.NET Core allows you to create Web Services based on gRPC ... which raises two questions: "What is gRPC?" and "Does it ever make sense to use it?" Here are Peter's answers.
Even though the groundbreaking .NET Core 3.0 is nearing general availability and the dev team has switched gears to focus on stability and reliability, new tweaks and enhancements are still appearing in the latest preview 8.
With .NET Core 3.0 becoming production-ready and transitioning from new features to a focus on stability and reliability in Preview 7, Microsoft has detailed a slew of new features for the ASP.NET and Blazor components.
You have two tools for generating your initial UI in a Blazor component: ASP.NET's Razor and Blazor's RenderFragment. Here's how to use both to integrate with your C# code (and a warning about what you can't do).