(Under construction) Aspire render modes

 Aspire render modes

 

This seems to be in flux. Especially in Aspire.











@rendermode InteractiveServer

 @rendermode InteractiveWebAssembly

 @rendermode InteractiveAuto = start with web socket connection, but as soon as user reloads the page or component then we will use WebAssembly.  It downloads the WASM files in the background. So now when reload then no web socket connection any more.  Only WASM files come from the cache.

 

Server 2

Renders a marker for a Blazor server-side application. This doesn't include any output from the component. When the user-agent starts, it uses this marker to bootstrap a blazor application.

ServerPrerendered 3

Renders the component into static HTML and includes a marker for a Blazor server-side application. When the user-agent starts, it uses this marker to bootstrap a blazor application.

Static 1

Renders the component into static HTML.

WebAssembly 4

Renders a marker for a Blazor webassembly application. This doesn't include any output from the component. When the user-agent starts, it uses this marker to bootstrap a blazor client-side application.

WebAssemblyPrerendered 5

Renders the component into static HTML and includes a marker for a Blazor webassembly application. When the user-agent starts, it uses this marker to bootstrap a blazor client-side application.

  • Static-SSR: A rendering type that can be chosen during development
  • Interactive-SSR: A rendering type that can be chosen during development
  • CSR: A rendering type that can be chosen during development
  • Auto Render Mode: A rendering technology that can enhance user experience and developer efficiency

Comments

Popular posts from this blog

Upgrading to .NET8 from desktop versions 4.8.X

GHL Chat Bots for Webpage

GHL > Set website so shorter URL address