Our Story
We started dotnet-guide.com in 2004 when .NET Framework 1.1 was still new. Back then, most resources either dumped you into thousand-page reference docs or gave you toy examples that didn't work in real projects. We wanted something different: tutorials you could actually run, compare against your own code, and finish in under an hour.
Over 20 years later, we're still here. The platform changed from .NET Framework to .NET Core to just .NET, but our approach hasn't: show working code, explain the decisions, and help you ship something real.
What Makes Us Different
Most tutorial sites focus on green-field projects. That's fine if you're starting fresh, but most of you are working with existing code. You need to know how to upgrade a .NET Framework 4.8 app to .NET 8, or why your old Web Forms patterns don't translate to Blazor.
We focus on that gap. You'll find side-by-side comparisons of old syntax versus new, migration checklists, and explanations of what changed and why. Our examples are small enough to understand quickly but complete enough to compile and run without extra setup.
We also avoid framework churn. If a tutorial covers ASP.NET Core 6, we flag it and link to the updated .NET 8 version. You won't waste time following outdated patterns.
How We Create Content
Every tutorial starts with a problem someone would actually face. We write the code, test it in Visual Studio or VS Code, and walk through the solution step by step. If Microsoft releases a new framework version, we review affected tutorials and update or archive them.
This site is maintained by an independent editor with industry experience and a small group of contributors. We earn revenue through light display ads and clearly labeled affiliate links, which never influence our technical recommendations.
You can suggest fixes or new topics anytime through the contact page. We read everything and often add requested content within a few weeks.
Independence Notice: dotnet-guide.com is an independent educational resource. We are not affiliated with, endorsed by, or connected to Microsoft Corporation. ".NET," "C#," "ASP.NET," "Visual Studio," and related names are trademarks of Microsoft. We use them here only to identify the technologies we cover.
We've been online since 2004 and have published over 300 tutorials and articles. Our content is linked by more than 150 websites across the web, including technology blogs and knowledge bases. That reach happened organically because people found the material useful, not through marketing spend or partnerships.
Frequently Asked Questions
Who runs dotnet-guide.com?
An independent editor and a small group of contributors. We keep the focus on the content rather than the personalities.
How do you earn revenue?
Light display ads and clearly labeled affiliate links. These never influence which technologies we recommend or how we present them.
How can I suggest a fix or new topic?
Use the contact page with a link to the page and a short note. We review all submissions and often respond within a few days.
Do you offer consulting or custom development?
No. We focus entirely on creating and maintaining educational content. For project work, check freelance platforms or local development agencies.
Why do some pages show framework version badges?
When a tutorial targets a specific .NET version, we label it so you know if it's current or legacy. Older content stays online for reference, but we clearly mark what's outdated.