Our Commitment
dotnet-guide.com is an independent educational resource for .NET developers. We have been publishing tutorials, guides, and articles for many years. Our editorial goal is straightforward: create technical content that is accurate, practical, and easy to follow so that developers can learn by building real things rather than reading theory.
Every piece of content on this site is published under the dotnet-guide.com brand. We stand behind it collectively, and we hold ourselves to the same standards across every tutorial and article we publish.
How We Create Content
Our editorial process is designed to produce content that developers can trust and use in real projects. Here is how a typical tutorial moves from idea to publication:
Topic Selection
We choose topics based on what .NET developers actually need. That means looking at common questions in the developer community, tracking new framework releases from Microsoft, and listening to reader suggestions submitted through our contact page. We prioritize topics where clear, hands-on guidance is hard to find elsewhere.
Research and Reference
Before writing begins, we research the topic using authoritative sources. Our primary references include official Microsoft documentation, .NET API references, the .NET team blog, GitHub source repositories, and published release notes. When a tutorial covers third-party libraries or tools, we verify against the official documentation for those projects as well.
Writing and Code Development
Tutorials are written with working code at the center. We build the example projects, test them in Visual Studio or VS Code, and walk through the solution step by step. Code samples are designed to compile and run with minimal setup so that readers can follow along directly. We use a combination of editorial writing and AI-assisted drafting tools to prepare content efficiently while maintaining quality.
Editorial Review
Every article goes through a human review before publication. Our team checks for technical accuracy, code correctness, clarity of explanation, and readability. We also verify that the content matches the .NET version it targets and that all code examples produce the expected output.
Where Our Information Comes From
We draw from publicly available, well-established sources in the .NET ecosystem. Our core references include:
- Microsoft official documentation (learn.microsoft.com)
- .NET API reference and SDK release notes
- The .NET Blog and ASP.NET Core Blog (devblogs.microsoft.com)
- GitHub repositories for .NET runtime, ASP.NET Core, and Entity Framework Core
- NuGet package documentation for third-party libraries covered in tutorials
- Published books and conference talks from recognized .NET practitioners
When we reference specific guidelines or recommendations, we link to the original source wherever possible so that readers can verify and explore further on their own.
Accuracy and Version Tracking
.NET is a fast-moving platform. Frameworks, APIs, and best practices evolve with each release. We take version accuracy seriously because outdated code examples can waste a developer's time or introduce problems in production.
How We Handle Versions
Every tutorial that targets a specific .NET version is labeled with a framework badge so readers know exactly what version the content covers. When Microsoft ships a new major release, we review affected tutorials and either update them to reflect the current version or clearly mark them as covering an older release.
Ongoing Content Updates
We periodically revisit published content to check for outdated patterns, deprecated APIs, or broken links. Tutorials that are no longer current remain online for reference but are marked accordingly so readers can distinguish between current and legacy material.
Accuracy & Currency (Content Notice)
We make reasonable efforts to keep tutorials and code examples accurate and current, but some technical details may be incomplete, incorrect, or become outdated as .NET evolves. Always verify key details against official Microsoft documentation and test code in your own environment before any production use. If you spot an issue, please contact us so we can review and update the content.
Use of AI-Assisted Tools
We use AI-assisted writing and development tools to help with drafting, code scaffolding, and research. We do not publish AI output as-is. Every article is reviewed and edited before publication, and key technical claims are checked against official documentation and/or tested in code.
Before anything goes live, we validate AI-assisted content for technical accuracy and .NET version compatibility. When code is included, we aim to compile/run examples, confirm NuGet/package versions, and update steps that change between .NET releases. Final decisions on what we publish are made by our editors.
Editorial Independence
Independence Notice: dotnet-guide.com is an independent educational website and is NOT affiliated with or endorsed by Microsoft. ".NET" is a trademark of Microsoft Corporation. Names are used solely for identification and educational purposes.
Our technical recommendations are based entirely on our own research, testing, and editorial judgment. We are not paid by any technology vendor to recommend their products or frameworks. When we mention specific tools, libraries, or services, it is because we believe they are genuinely useful for the topic at hand.
dotnet-guide.com earns revenue through display advertising and clearly labeled affiliate links. These commercial relationships never influence which technologies we recommend, how we review a tool, or what we include in our tutorials. Advertising and editorial decisions are kept separate.
What We Are (and What We Are Not)
We are a technical education site that helps .NET developers learn through practical, hands-on tutorials and articles. Our content is designed to explain concepts clearly and provide working code you can use as a starting point in your own projects.
We are not a consulting firm, a software vendor, or an official training provider. Our tutorials are for educational purposes and should be adapted and tested before use in production systems. For project-specific guidance, we recommend working with qualified professionals.
Corrections and Feedback
We take accuracy seriously, but mistakes can happen. If you spot a technical error, an outdated code example, or something that could be explained more clearly, we want to hear about it.
Please reach out through our Contact page with a link to the article and a brief description of the issue. We review all submissions and make corrections as quickly as possible. Significant updates are noted on the affected article so readers know the content has been revised.
Frequently Asked Questions
Who writes the content on dotnet-guide.com?
All content is published under the dotnet-guide.com brand and reviewed by our editorial team. We focus on hands-on .NET development experience and practical testing, rather than individual bylines. We focus on the quality of the content rather than individual bylines.
How do you keep tutorials up to date?
We monitor .NET releases and periodically review published tutorials. When a new framework version introduces breaking changes or better approaches, we update the affected content or mark it as covering an older version. Each tutorial displays the edition year so you can see when it was last reviewed.
Do advertisers or sponsors influence your content?
No. Our editorial recommendations are independent. Advertising revenue supports the site, but it never affects which tools, libraries, or patterns we recommend in our tutorials. Commercial and editorial decisions are handled separately.
Can I use code from your tutorials in my projects?
Yes. Code examples on dotnet-guide.com are provided for educational purposes and you are free to use, modify, and build upon them in your own projects. Code is provided “as is” without warranties, and you are responsible for testing, security review, and production readiness before deploying.
How can I suggest a topic or report an error?
Use the Contact page with a link to the relevant article and a short description. We review all submissions and aim to respond as soon as possible.