
Practical insights from real-world cloud, data, and applied AI systems
When working with Blazor WebAssembly, JavaScript interop often feels straightforward—until it isn’t. One of the more subtle (and frustrating) issues I’ve run into involves Safari, user-initiated navigation, and async event handlers. This post documents a real-world lesson learned: why I intentionally avoid async when triggering browser navigation (like mailto:) from Blazor, even though async/await is…
Categories:
Written by
on
This is a continuation of earlier article where we implemented monitoring output as JSON. We are going to build Angular Component that…
Categories:
Written by
on
stuck with this compilation error for a while. Suppose we have this property defined; public result = Result If we want to…
Categories:
Written by
on
Let’s get our hands in some code. This web app will act as a monitoring and reporting service that will check the…
Categories:
Written by
on
In our previous article, we have crated a health-check application. This time we would be trimming down the component list to see…
Categories:
Written by
on
ADO ai angular asian asp.net asp.net core azure ACA azure administration Azure Cloud Architect Azure Key Vault Azure Storage Blazor WebAssembly BLOB bootstrap Branch and Release flow c# c#; ef core css datatables design pattern docker excel framework Git HTML JavaScript jQuery json knockout lab LINQ linux powershell REST API smart home SQL Agent SQL server SSIS SSL SVG Icon typescript visual studio Web API window os wordpress
The information on this weblog is provided “as is,” without warranties of any kind, and confers no rights. The content reflects my personal views and does not represent the thoughts, intentions, plans, or strategies of any organization with which I am affiliated. Discussion and differing viewpoints are welcome; however, I reserve the right to moderate or remove comments that are abusive, profane, rude, or anonymous. Please keep the conversation respectful and constructive.