Blazor is a .NET-based Component Architecture platform that is offered as a potential alternative to other modern frameworks such as Angular or ReactJS for responsive web development.
If you are familiar with other Component Architecture frameworks and are also a .NET developer then moving to Blazor should be fairly straightforward. But, there are some caveats and design constraints you should consider in Blazor that you might not worry about in other frameworks.
A simple code snippet that allows tool-tips to be displayed on HTML controls when the mouse hovers over them or when the control is clicked (e.g. touched on a mobile device). Useful in scenarios where you want a simple, modern, tool-tip without the weight of a 3rd party library.
IISExpress, bundled with Visual Studio, provides a lighter-weight web server than the full IIS (Internet Information Services) Windows service, and is useful for running up and debugging web code projects.
When working on multi-developer projects, if each developer machine isn’t configured the same way developers can waste a lot of time editing connection strings, local machine name, and other settings when pulling code projects from source code control. On ASP.NET code projects, you can configure per-machine configuration overrides to overcome this.
I’ve regularly witnessed strange behaviour on one of our SharePoint environments where the ABOUT screen for an installed SharePoint Add-in shows an error message (like the screen-shot below) of ‘Sorry, apps are turned off’ when you first navigate to it after not doing so for a while (10 mins or more). Doing a web browser refresh on the page normally fixes it, but it was annoying so I invested a bit further.
There can be many reasons for SharePoint CAML queries not working, but one of the most frustrating ones is “The underlying connection was closed: The connection was closed unexpectedly.” The connection from the client (CSOM/REST API) is just dropped. Debugging the issue can seem, at first, almost impossible as there is nearly no additional data to work with, but sometimes the solution can be fairly straightforward.
If you work with SharePoint custom site templates regularly, and your organisation has separated development, test, and production environments, then you’ll probably have come across the issue where a custom site template you’ve saved in one environment as a solution package (WSP) uploads and activates fine in another environment but then fails with the familiar obscure message and correlation ID when you attempt to create a new site.
Sometimes the easiest way to resolve a missing SharePoint Solution dependency is simply to install it again. Often the solution package (WSP) is available on your development or test environment, but how do you download it from there? For sandboxed solutions, you can just go to the ‘Solutions’ section in Site Settings, but what about farm solutions?!
Whenever SharePoint (SP) is patched tests are run on the farm’s content databases (CDB) to check for issues. In most cases, patching can proceed without adversely affecting the farm but it never hurts to have a perfect and functional an environment as possible before making any changes. This article guides you through how to manually run the same CDB tests, and diagnose and fix any issues/errors that are reported.
Most of the time you shouldn’t need to get involved in anything like this, but upgrades/patches can often queue up one-time timer jobs that don’t get executed for some reason and can hold off other jobs (such as Add-in management) so they don’t run.