ASP.NET Core 7.0 Documentation
ASP.NET Core 7.0 https://learn.microsoft.com/en-us/aspnet/core/introduction-to-aspnet-core?view=aspnetcore-7.0 ASP.NET Core Blazor https://learn.microsoft.com/en-us/aspnet/core/blazor/?view=aspnetcore-7.0
Author
Secure a hosted ASP.NET Core Blazor WebAssembly app with Microsoft Entra ID
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/hosted-with-microsoft-entra-id?view=aspnetcore-7.0 Walkthrough The subsections of the walkthrough explain how to: Create a tenant in Azure Register a server API app in Azure Register a client app in Azure Create the Blazor app Modify the Server appsettings.json configuration Modify the default access token scope scheme Run the app Create a tenant in Azure Follow the guidance in Quickstart: Set up... » read more
Azure AD is now Microsoft Entra ID
Microsoft has reamed Azure Active Directory (Azure AD) to Microsoft Entra ID for the following reasons: (1) to communicate the multicloud, multiplatform functionality of the products, (2) to alleviate confusion with Windows Server Active Directory, and (3) to unify the Microsoft Entra product family. https://entra.microsoft.com/#home References: https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name
What is the usage of UPDLOCK in Select and Update statement
The function of using UPDLOCK is to allow users to read data first (and not to block other users from reading data), and to ensure that when the data is updated later, the data has not been modified by other users during this period of time. When this option is selected, SQL Server uses a... » read more
Convert Syncfusion Blazor WebAssembly App from Syncfusion 19.x to 23.x
To update to a new version of Blazor WebAssembly, you need to follow 4 steps: Change the target framework. Upgrade NuGet packages. Add HeadOutlet to Program.cs. Modify Blazor “Server” App Change the target framework The first step to update Blazor WebAssembly to a newer version is updating the target framework. Right click to your project, select Properties. Do this... » read more
Install .NET workload wasm tools for Syncfusion Essential Studio
Install Syncfusion Essential Studio… .NET Core SDK 6.0 or later – installed.NET workload wasm-tools – not installed.NET workload wasm-tools-net6 – not installed Need to install .NET workload wasm-tools as prerequisite to using Syncfusion Blazor WebAssembly demo. C:\Users\xxxxx>dotnet workload listC:\Users\xxxxx>dotnet workload install wasm-toolsC:\Users\xxxxx>dotnet workload install wasm-tools-net6 References: https://stackoverflow.com/questions/74730565/how-to-check-if-a-workload-is-installed-on-clients-visual-studio
syncfusion-blazor.min.js script file not found in application.
When upgrading from existing Syncfusion BLazor app, the _content does not get generated. The workaround is to download the js script file and reference it directly. Issue: The following file in the _content folder is unable to be loaded from the app. Fix: Download file (input specific version) and reference in your project directly Reference:... » read more
Convert Blazor App from .NET 5 to .NET 6/7
To update to a new version of Blazor WebAssembly, you need to follow 4 steps: Change the target framework. Upgrade NuGet packages. Add HeadOutlet to Program.cs. Modify Blazor “Server” App Change the target framework The first step to update Blazor WebAssembly to a newer version is updating the target framework. Right click to your project, select Properties. Select .NET... » read more
SQL Availability Group Setup – The local node is not part of quorum
Problem While trying to set up a couple of SQL Enterprise servers in an Availability Group I kept getting the message “The local node is not part of quorum and is therefore unable to process this operation” I had already set up Windows Failover Clustering with a cloud witness for the quorum. and ticked “Enable AlwaysoOn... » read more
Not able to see a list of job history due to incorrect server name
Issue: When a server is created via replication, the sql server name might need to be changed. If not, you will see login issues in the database log and unable to see the job history. Resolution: Remember to restart SQL Server to apply the change.