Blazor WebAssembly with MongoDB is a course in building web applications entirely in C#, with Blazor WebAssembly on .NET 10 for the interface and MongoDB 8 for data, covering document design, the MongoDB C# Driver, Razor components, forms, routing and connecting safely through a Web API. It suits C# and ASP.NET Core developers and IT teams building internal systems.
Blazor lets C# developers build interactive web pages using the same language on the front end and the back end, and Blazor WebAssembly runs .NET code directly in the browser. Paired with MongoDB, which stores flexible documents, it makes web applications quick to build and comfortable with data whose shape changes often. Blazor has changed a great deal since .NET 8, however, with the idea of render modes, and the MongoDB C# Driver has moved to version 3, so many older examples no longer work.
This course starts with MongoDB 8 and C#: document design, CRUD with the MongoDB C# Driver, LINQ, the aggregation pipeline, indexes and GridFS. It then builds Blazor WebAssembly on .NET 10, from the project structure, Razor components and data binding to passing data between components, forms with validation and routing. Learners then connect Blazor to MongoDB safely through an ASP.NET Core Web API, with authorisation and JavaScript interop. It closes with a workshop that builds and deploys a real web application. (3 days, 6 hours per day, 18 hours in total, Intermediate level.)
Course Details
This course is the 2026 edition that replaces the previous Blazor WebAssembly with MongoDB course. It has been rewritten from scratch for .NET 10 (LTS), MongoDB 8 and the current MongoDB C# Driver. It runs for 3 days, 6 hours per day (18 hours in total, 09:00-16:00), as lectures with labs built on a single sample store application throughout. Intermediate level. It explains Blazor render modes on .NET 10, uses the official driver instead of the MongoDB.Entities add-on library, connects Blazor to MongoDB through an ASP.NET Core 10 Minimal API, and adds document design, authorisation, performance tuning and Docker. Every lab uses MongoDB on the learner's own machine. Learners take home a lab guide, source code for every lab and docker-compose files.
Section 1: Lab: Introducing NoSQL and MongoDB 8
Section 2: Designing Documents for How They Are Used
Section 3: Lab: CRUD with the MongoDB C# Driver
Section 4: LINQ and the Aggregation Pipeline
Section 5: Indexes, GridFS and Security
Section 6: Blazor on .NET 10
Section 7: Lab: Creating a Blazor WebAssembly App
Section 8: Razor Components and Data Binding
Section 9: Lab: Composing Components and Managing State
Section 10: Lab: Forms with EditForm
Section 11: Routing and Navigation
Section 12: Lab: A Web API Backed by MongoDB
Section 13: Authentication and Authorisation
Section 14: JavaScript Interop and Performance
Section 15: Workshop: A Complete Store Web App and Deployment
No public rounds are open right now. Join the waiting list and we will contact you first when the next round opens, or ask us on LINE. Or call 02-570-8449 or 088-807-9770
Since .NET 8 both are render modes of a Blazor Web App. Interactive Server runs code on the server and sends UI updates over a real-time connection, so it starts quickly but needs a constant connection. Interactive WebAssembly downloads the .NET runtime and runs in the browser, which moves work to the client and lightens the server load, but the first load takes longer. There is also Auto mode, which starts on the server and switches to WebAssembly once it has downloaded. If you want the whole app to run purely in the browser, you can build a standalone Blazor WebAssembly app.
Pass data from parent to child with properties marked with the Parameter attribute, and send events or values from child to parent with EventCallback. For two-way binding, use @bind with a parameter that has a matching EventCallback whose name ends in Changed. For data many components share, use a cascading value or a state container service registered through dependency injection, and treat parameters as values the child does not change itself.
Blazor WebAssembly code is downloaded and runs entirely in the browser, so any connection string you include is visible to every user and grants full access to the database, and browsers cannot open the kind of connection MongoDB uses anyway. The right approach is an ASP.NET Core Web API that uses the MongoDB C# Driver on the server, checks permissions and validates input, with Blazor calling it only through HttpClient.
It suits C# and ASP.NET Core developers who want to build web front ends with Blazor, developers who want to use MongoDB with .NET, and IT staff who build internal systems. You should be able to write C#, have a basic grasp of LINQ and async/await, have some experience with ASP.NET Core MVC or Web API, and know basic HTML and CSS.
You will be able to design documents and use MongoDB 8 from C# for CRUD, LINQ and aggregation, build Blazor WebAssembly apps on .NET 10 with Razor components, validated forms and routing, connect them safely to MongoDB through a Web API, apply user permissions and deploy with Docker. Participants who complete the training receive a Certificate of Completion with its own number, which can be verified online.
Yes. It can be run in-house for your team, with examples adapted to your work, such as a data structure similar to your real systems, or a focus on moving older Blazor apps to .NET 10. You can request a quotation from this page, or contact us on LINE @itgenius or by phone on 02-570-8449.
Almost every business application reads and writes a database. Many .NET developers still maintain code built on DataSets, older Entity Framework versions on .NET Framework or LINQ to SQL, which is no longer developed, while new systems use Entity Framework…
ASP.NET Core is Microsoft's main framework for building web applications and APIs on .NET, and it runs on Windows, macOS and Linux. Today .NET 10 is the LTS release that organisations choose for the long term, yet many books and code samples still follow the…
Microservices split a large system into smaller services that can be developed, deployed and scaled independently. Each service owns its database and talks to others through APIs or messages. Teams can work in parallel and change one part at a time, but this…
