Practical C Projects with .NET Sharpen your C and .NET skills to build fun console, web, game, and AI apps with modern tools… (Matt Eland, Kevin Griffin)（Z-Library）

【One-Line Pitch】 A hands-on project book that turns intermediate C# knowledge into real, finished applications—console games, web APIs, AI chatbots, and MonoGame titles—so you learn modern .NET by building rather than by reading theory. Best for developers who can already program in C# but freeze when facing a blank project. 【Book Arc】 - **Opening (~0%–10%)**: Sets the premise—side projects as the fastest path from "I can code" to "I can build things"—and frames the reader as someone comfortable with C# basics, async, and request/response models. - **Early (~10%–30%)**: Part 1 builds console fundamentals through an adventure game (Spectre.Console, OOP, exception handling, unit tests), an Enigma machine (Chain of Responsibility, test-driven design), procedural world generation with Perlin Noise, and a JSON-driven RPG combat system using the strategy pattern and dependency injection. - **Middle (~30%–60%)**: Part 2 shifts to web, mobile, and desktop—ASP.NET Minimal APIs with Entity Framework and SQLite, JWT auth, the REPR pattern, AutoMapper, and Uno Platform for cross-platform UI. - **Late (~60%–75%)**: Part 3 introduces AI projects: conversational partners via Ollama and Microsoft.Extensions.AI, prompt engineering, function calling and RAG, an AI librarian with Microsoft Agent Framework, and ML.NET regression with AutoML and IoT data. - **Ending (~75%–100%)**: Part 4 covers MonoGame—recreating Pong, then scaling to a battle arena with graphics, collisions, and AI—before a closing chapter on scoping, starting, and finishing your own side projects. 【Key Takeaways】 - **Projects are meant to be built, not followed** (Early): The preface and foreword stress that each project is a starting point for your own modifications, not a polished artifact to copy. This is the book's core pedagogical stance. - **Design patterns emerge from real problems** (Early): Chain of Responsibility, strategy pattern, and dependency injection appear as solutions to concrete needs in the Enigma machine and RPG chapters, not as abstract theory. - **Testing is woven into construction** (Early): Unit tests appear alongside implementation—testing console input/output, rotor mappings, and end-to-end Enigma behavior—rather than as an afterthought. - **Modern .NET spans far beyond the console** (Middle): The same C# skills carry into Minimal APIs, Entity Framework, SQLite, JWT authentication, and the REPR pattern, showing the breadth of the platform. - **AI integration is treated as a practical .NET concern** (Late): Ollama, Microsoft.Extensions.AI, function calling, RAG, and ML.NET are presented as libraries and patterns you wire into applications, not as research topics. - **Game development gets a full cross-platform treatment** (Ending): MonoGame is positioned against Unity and Godot, with Pong as the entry point and a battle arena as the scaling exercise. - **Finishing matters as much as starting** (Ending): The final chapter addresses scoping, focusing statements, repositories, READMEs, and task-by-task progress—the unglamorous discipline of shipping side projects. 【Reading Tips】 - **Skim the preface and technical requirements** (~5%–10%) if you already know C# and async; the real value starts in Chapter 1. - **Deep-read the console chapters** (~10%–30%) even if you plan to skip ahead—the OOP, testing, and pattern foundations recur throughout the book. - **Type the code yourself** rather than copying from the GitHub repository; the preface explicitly recommends this to avoid errors and build muscle memory. - **Treat each project as a launchpad**: after finishing a chapter, pick one modification the author suggests and implement it before moving on. - **Don't skip Chapter 14** (~95%) if your goal is actually finishing a side project—it's short but addresses the psychological and organizational barriers. 【Coverage Limits】 The excerpts cover the table of contents, preface, and early chapters in detail, but later chapters (Uno Platform, AI librarian, ML.NET, MonoGame implementation) are represented mainly by headings and brief descriptions. Specific code patterns, pitfalls, and chapter-level insights from the second half are not fully visible in the source material.