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 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
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
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
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
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.
Shrink Database (DbccFilesCompact) Database -> Right Click -> Tasks -> Shrink -> Database Example: 3 hrs to Shrink 1,100 GB data file to 296 GB.
https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2022?view=sql-server-ver16 https://sqlserverbuilds.blogspot.com/2014/01/sql-server-2014-versions.html Upgrades from earlier versions to SQL Server 2022 SQL Server 2022 (16.x) supports upgrade from the following versions of SQL Server: SQL Server 2012 (11.x) SP4 or later SQL Server 2014 (12.x) SP3 or later SQL Server 2016 (13.x) SP3 or later SQL Server 2017 (14.x) SQL Server 2019 (15.x) Note: Need to... » read more
Error: Login failed for user ‘DomainName\ServerName$’. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>] Possible Causes: User application that is accessing this database is running under the default Windows service account. Check the user application in Services and make sure it is running under a specific service account and not... » read more