
Listed as Free on Udemy when checked on 7 November 2026. No coupon or subscription trial is required for the listed lessons. Enrollment needs a Udemy account; availability can change.
About this course
A small task list gives programming concepts somewhere visible to live. A button can create an item, a checkbox can change its state, and a class can hold the information that the page displays. This free course offers a focused way to connect those ideas when you are ready to move beyond isolated C# examples.
Jonas Fagerberg teaches the second part of his beginner series through a browser-based to-do application. The recorded project uses C# 10, .NET 6 and Blazor WebAssembly, with HTML and Razor for the interface. Its central learning opportunity is comparison: first follow the working page, then consider how moving responsibilities into a separate class changes the organization of the same application.
| Official course | C# 10 with .NET 6 for Beginners (Part 2) – To-do Application |
|---|---|
| Created by | Jonas Fagerberg |
| Platform | Udemy |
| Language | English |
| Level | Beginner |
| Listed duration | 114 minutes; 19 lectures across 5 sections |
| Completion terms | Not included with a new free enrollment |
What you’ll learn
Follow a compact development sequence from project setup to an interactive task list and a later refactoring. The topics bring together objects, collections, event handlers, textbox binding, conditional styling and exception handling. Look for the connection between a user action, the method it invokes and the information that changes, rather than measuring progress only by whether the page looks finished.
Skills you’ll gain
- C# object modeling
- Collection operations
- Razor event handling
- Textbox data binding
- Class responsibility
- Debugger navigation
A manageable project with two passes
The five sections contain 19 videos, totaling about 114 minutes. Setup and interface work lead into two iterations of the application, with source-control steps included around the project. Basic C# familiarity is useful before starting: this is Part 2, and the instructor recommends his earlier theory course or equivalent knowledge. Treat that earlier course as separate preparation, not as additional lessons included in this listing.
In the first pass, page markup and C# behavior sit close together. That makes the route from an interface element to its handler easier to follow. In the second pass, a class named TodoFactory takes on responsibilities previously kept in the Razor component. Comparing the versions can help you ask which code belongs to presentation and which code manages the collection, without turning a small teaching example into a universal architecture rule.
Make the behavior explainable
When an item is marked complete, distinguish its stored completion state from the CSS that displays a line through its text. A visual change and a change to application data are related, but they are not interchangeable. The same distinction helps when reading an add or delete method: identify the collection being changed before looking at how the page redraws the result.
Textbox binding is another useful place to slow down. Ask when the typed value reaches the C# variable and which value the add method actually reads. A null guard also answers a narrower question than an empty-list check: an existing collection can contain no items. These distinctions make debugging more systematic because they give you specific assumptions to inspect instead of repeatedly changing unrelated lines.
Read the recorded environment in context
The material was last updated in 2022. Microsoft ended support for .NET 6 in November 2024, so the recorded setup should be treated as a historical learning environment. Consult current documentation and use a supported platform for new work; matching every installer screen or project template is not guaranteed. Learning the structure of an event handler does not require treating an old runtime as a current deployment recommendation.
This project is a practice application, not a complete service design. The listed scope does not establish database persistence, account security or production deployment. In particular, a collection in memory should not be assumed to preserve tasks after a refresh. The GitHub lesson concerns source control; it does not by itself demonstrate storage for the application’s users. Repository contents and their present availability are not promised here.
Try a small tracing exercise
For an optional study exercise, sketch a fictional list with two tasks. Trace what should happen when you add a third, complete the first and delete the second. Beside each action, write the state before and after it, the responsible method and the visible result. Repeat the sketch after the refactoring and compare which responsibilities moved. This is an editorial exercise, not an advertised assessment or a claim that the repository has been tested.
Allow extra time beyond the recordings for notes and debugging. Pause when you can no longer explain a change in state, then inspect the relevant variable or method before continuing. Free access applies to the listed Udemy lessons; it does not promise a completion certificate, paid development tools or hosting.
Microsoft .NET support information: Check supported releases before choosing a development environment. Blazor event handling: Compare event syntax with current documentation.
Related courses for your next step
- Build a stronger foundationFree C# Data and Methods Course
Review data and methods in a separate introductory course.
Beginner
- Explore a later projectFree Blazor CRUD Course
Move on to a separate book-catalog example involving EF Core.
Intermediate
Frequently asked questions
Is this a first course in programming?
It is beginner level, but it is Part 2 of a series. Basic C# knowledge or the separate earlier theory course is recommended.
Will the task list keep data after a refresh?
The listed curriculum does not establish persistent storage. Do not assume that an in-memory collection saves user data between sessions.
Can I use the recorded .NET 6 setup for a new production service?
Treat the 2022 setup as historical. .NET 6 is out of Microsoft support; new work needs a supported environment and additional design, security and deployment work.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.