Browser storage For transient data that the user is actively creating, a commonly used storage location is the browser’s localStorage and sessionStorage collections: localStorage is scoped to the browser’s window. If the user reloads the page or closes and re-opens the browser, the state persists. If the user opens multiple browser tabs, the state is shared across the tabs. Data... » read more
In-memory state container service Nested components typically bind data using chained bind as described in ASP.NET Core Blazor data binding. Nested and un-nested components can share access to data using a registered in-memory state container. A custom state container class can use an assignable Action to notify components in different parts of the app of state changes. In the following... » read more
Where to persist state Common locations exist for persisting state: Server-side storage URL Browser storage In-memory state container service Server-side storage For permanent data persistence that spans multiple users and devices, the app can use independent server-side storage accessed via a web API. Options include: Blob storage Key-value storage Relational database Table storage After data... » read more
Examples A. Checking a specific table The following example checks the data page integrity of the HumanResources.Employee table in the AdventureWorks2012 database.SQLCopy B. Performing a low-overhead check of the table The following example performs a low overhead check of the Employee table in the AdventureWorks2012 database.SQLCopy C. Checking a specific index The following example checks a specific index, obtained... » read more
Using Kudu First, let’s launch Kudu. You can do this in a variety of ways. Here are a few: Launch Kudu manually from the address bar If your website is https://magicalunicorns.azurewebsites.net, the Kudu URL is https://magicalunicorns.scm.azurewebsites.net. Notice the appended “scm.” here. You’ll need to be signed in with an account with access to the App Service resource... » read more
Publish in Visual Studio. “Remove additional files at destination” option Remove additional files at destination The most common and easiest way to resolve this error is to re-publish your code, but with the options to “Remove additional files at destination” turned on. This will ensure that Visual Studio’s web deploy process will delete all existing... » read more
https://learn-blazor.com/architecture/rest-api/ https://github.com/software-architects/learn-blazor/tree/master/samples/RestApi
Error: Running a query and got this error… An inconsistency was detected during an internal operation. Please contact technical support. Fix: DBCC CHECKDB (‘DMS’) WITH NO_INFOMSGS, ALL_ERRORMSGS DBCC CHECKDB(‘DMS’, REPAIR_REBUILD) dbcc CHECKDB(‘DMS’, REPAIR_ALLOW_DATA_LOSS) Sources: https://dba.stackexchange.com/questions/11235/an-inconsistency-was-detected