Blazor C# Vocab

Question 1

Word

Answer 1

Definition

Question 2

Blazor Component

Answer 2

An element of UI. Built in C# classes that handle user events, define flexible UI rendering logic, can be nested and reused, can be shared and distributed. Usually written in the form of a Razor markup page (.razor).

Question 3

Razor

Answer 3

A syntax for combining HTML markup and C# code designed for developer productivity. Allows you to switch between HTML and C# in the same file.

Question 4

Document Object Model (DOM)

Answer 4

The Data representation of the objects that compromise the structure and content of a document on the web. It is a programming interface, this allows programming languages to interact with the page.

Question 5

Script

Answer 5

A program run by a browser.

Question 6

Document

Answer 6

The root document of the DOM itself.

Question 7

Node

Answer 7

Every object located within a document is a node of some kind. (Element node, text node, attribute node).

Question 8

Element

Answer 8

An element or node of type element returned by a member of the DOM API. (table elements, h1 elements, etc). node → Element (inherits form node).

Question 9

NodeList

Answer 9

An array of elements. Accesible by index. (list.item(1), or list[1]).

Question 10

Attr

Answer 10

An object reference that represents a special interface. Attributes are nodes in the DOM like elements.

Question 11

NamedNodeMap

Answer 11

Similar to an array, but items are accesed by name or index. You can add and remove items from a namedNodeMap.

Question 12

Window Object

Answer 12

represents something like the browser.

Question 13

Blazor

Answer 13

.Net frontend web framework that supports both server-side rendering and client interactivity in a single programming model.

Question 14

Interactive SSR

Answer 14

Interactive server side rendering is where the server processes the initial request, generating the complete HTML for a page and sends it to the client. Allows users to see content faster.

Question 15

Client-Side Rendering (CSR)

Answer 15

The client is responsible for rendering the content and handling all interactions. Server sends minimal HTML shell and JavaScript files that execute on the client side to build and manage the UI. Blazor Web Apps supports this with .NET runtime built with WebAssembly.

Question 16

SignalR

Answer 16

A library that enables real-time, two-way communication between client and server in web applications, commonly used for live updates like chat, notifications, or dashboards.

Question 17

Lambda Expression

Answer 17

An anonymous method/function that can contain expressions or statements. It’s commonly used for defining short blocks of code that can be passed as arguments to functions like LINQ methods (Where, Select, etc.) or for event handling

Question 18

Static Server Rendering

Answer 18

Server generates HTML content at build time (before any requests). The HTML content is then served to the client as is, without requiring any further processing.

Question 19

Dynamic Server Rendering

Answer 19

The server generates the HTML content for each request in real time.

Question 20

Single Page App

Answer 20

A web app that loads a single HTML page, and dynamically updates through the DOM. SPAs manage routing, data fetching, and UI rendering within the browser itself.

Question 21

Blazor Web Assembly

Answer 21

Apps execute entirely on the user’s browser. No need for server-side rendering, behaves more like a SPA application

Question 22

MVC Model

Answer 22

Models, Views, Controllers. Controller processes incoming requests, manipulates the Model, and returns the appropriate View to user. This is common in ASP.NET. HTML Page is rendered server-side and sent back to the client.

Question 23

Blazor Server

Answer 23

UI logic runs on the server side, and the HTML is dynamically generated and sent to the client in real-time through SingalR.

Question 24

JavaScript Interop

Answer 24

A library that allows Blazor components to call JavaScript functions and vice versa, enabling interaction between Blazor and JavaScript code.

Question 25

Pre-rendering

Answer 25

A feature that allows the initial HTML of a Blazor component to be rendered on the server before it becomes interactive on the client-side.

Question 26

CRUD

Answer 26

Create, Read Update, Delete. These are the basic operations you perform on data in a database or a system for back-end work.

Question 27

WebAssembly

Answer 27

A low-level binary format that allows code written in languages like C#, C++, or Rust to run in web browsers at near-native speed, enabling efficient client-side applications in Blazor WebAssembly

Question 28

Namespace

Answer 28

A Container that organizes classes, interfaces, structs and enums. Helps avoid naming conflicts by logically grouping related code.

Question 29

Entity Framework

Answer 29

An object-relational mapper (ORM) for .NET that allows .NET objects to interact with SQL databases using C# and LINQ, simplifying database operations like queries and updates.

Question 30

Progressive Web Application

Answer 30

This is a web application that has the capabilities of delivering an app-like experience to users. Designed to be fast, reliable and work offline. They are able to be installed on a device and provide push notifications.