Manage CosmosDB objects (Stored Procedure, Functions, Triggers …) with this Nuget package
Handling Exception in Blazor
Like in every part of your system, on the front-end part you should take care of exceptions. Like its name says : it should not happen. But we are not perfect and they happen because of a lot of reasons. For now exceptions that happens in Blazor are sent to the browser console. But we might need more than that : display it on the web page or even send it to our backend for alerting the team that something went wrong.
How to create a Nuget package for Blazor assembly with Azure DevOps
How to validate incoming command with reCaptcha on a Blazor app with a ASPNET Core backend with MediatR
The Toss project is a message board : people register and then they send messages. One of the threat with this kind of application are robot : people creates program that creates new account and then post spam message.
Setup an Azure DevOps CI pipeline with E2E tests against a ASPNET Core server
In my project Toss, I have classic Unit / Integration test but also end-to-end tests with Selenium WebDriver. I need those test for 2 reasons :
You always need them :) Because it’s the last step of integration, and you can’t think of all the things that could go wrong when you write your unit / integration tests. Here you are 99% sure that the basic usage of your app is not broken by a build.
Blazor is an experimental technology with new version every 1-2 months that could introduce breaking changes. I need a way to know that after an upgrade my app is still ok.