Skip to main content

Disclaimer

Last Updated: October 13, 2026

Independence Notice

Important: dotnet-guide.com is an independent educational website. It is not owned, operated, sponsored, affiliated with, or endorsed by Microsoft Corporation.

We publish independent tutorials about .NET, C#, Microsoft technologies, open-source libraries, and related development tools. Mentioning a technology, linking to its documentation, or using its software in a demonstration does not establish a partnership with its owner.

Trademarks and Third-Party Names

Microsoft, .NET, C#, ASP.NET, Visual Studio, Azure, and other Microsoft product names or marks referenced here belong to Microsoft Corporation or their respective rights holders. Names such as Model Context Protocol, MCP, and third-party library or provider brands may be associated with other organizations.

We use product and technology names to identify what a tutorial covers and to explain compatibility, APIs, and implementation choices. All trademarks and logos remain the property of their respective owners. Their appearance on this site does not imply sponsorship, authorization, or endorsement.

Descriptive References

References to third-party technologies are intended for identification, technical explanation, commentary, and education. Any rights to reproduce third-party material depend on applicable law, licenses, permissions, and the circumstances of use; educational purpose alone does not automatically grant permission.

Educational and Informational Purpose

Articles, tutorials, diagrams, configuration files, and example applications on dotnet-guide.com are intended to help developers learn and explore software development concepts. They are provided for general education and information, not as a promise that a given solution will be suitable for a particular project.

Readers should independently assess any instructions or examples before adopting them in a personal, commercial, regulated, or production environment.

Technical Accuracy, Versions, and Updates

Content currency notice: This site contains tutorials written across multiple generations of .NET. Some older articles may describe APIs, frameworks, packages, or practices that have changed or been superseded. A tutorial should be read in the context of its stated target version and publication or review date.

We make reasonable efforts to research and improve our material, but we cannot guarantee that every page is complete, current, accurate, or compatible with every environment.

  • Version-specific behavior: .NET SDKs, NuGet packages, APIs, operating systems, and hosting platforms may differ from the environment used for an example.
  • Dependency changes: Third-party SDKs, services, models, and packages may introduce breaking changes, become unavailable, or alter their terms.
  • Historical content: Some older tutorials may remain available for learning or reference even when a newer approach exists.
  • Update limitations: We do not promise that every article will be revised immediately after a release or that all external links will remain available.

Check official documentation, release notes, security advisories, and the versions actually installed in your environment before relying on technical guidance.

Code Samples, Verification, and GitHub Repositories

Some newer tutorials, including selected guides in our .NET AI tutorial collection, are supported by public GitHub companion projects. Those projects may include pinned SDK or dependency versions, build results, automated tests, integration checks, and documented verification evidence.

Verification statements describe what was tested, with which versions and environment, at the time of the recorded run. A successful restore, build, test suite, or CI job does not prove that every configuration works, that an application is free of defects, or that its security, performance, reliability, and production-readiness have been established.

Where a tutorial distinguishes deterministic tests, local integration checks, live-provider runs, and CI checks, those categories should not be treated as interchangeable. A provider adapter that compiles successfully, for example, is not necessarily verified against a live external service.

Availability and results may change when dependencies, cloud services, SDK versions, or external providers change. Review the relevant repository files and repeat appropriate tests in your own environment before relying on a sample.

AI, Agents, and Model Context Protocol Examples

Our AI-related tutorials may discuss Microsoft.Extensions.AI, retrieval systems, tool-using agents, Model Context Protocol (MCP), and integrations with local or hosted model providers. These are educational demonstrations of particular architecture and API patterns, not endorsements or guarantees of any provider, model, or service.

  • Model outputs: AI-generated text, decisions, and tool selections can be incorrect, incomplete, misleading, inconsistent, or affected by model and prompt changes.
  • Illustrative data: Synthetic incidents, runbooks, service records, and example responses are demonstrations, not live operational findings or validated advice for a real system.
  • Verification boundaries: Deterministic tests of a store, tool, client, or protocol exchange do not establish that an LLM will always behave correctly when connected to that component.
  • External services: Using an API or hosted model may incur charges, rate limits, availability restrictions, and privacy or data-retention obligations set by the provider.
  • Autonomous actions: Any deployment of agents or tool-capable systems requires independently designed permissions, input validation, authorization, monitoring, error handling, and human oversight where appropriate.

Do not submit credentials, personal information, proprietary source code, or other sensitive data to an external service without first reviewing the service's terms, data practices, and your organization's requirements.

Security and Production Deployment

Educational samples often simplify infrastructure, error handling, observability, authentication, authorization, secret management, deployment, and resilience so the main concept is easier to understand. Such omissions are not recommendations for production systems.

Before using any sample beyond a controlled learning environment, assess the threat model and application requirements, review dependencies and licenses, protect credentials, validate all untrusted inputs and outputs, test failure scenarios, and perform appropriate security, performance, and operational reviews.

Not a production certification: A companion sample marked as verified or passing CI is not certified secure, compliant, or ready for production deployment.

No Warranties

To the extent permitted by applicable law, this website and its content are provided "AS IS" and "AS AVAILABLE" without warranties or representations of any kind, whether express or implied, including warranties relating to:

  • Accuracy, currency, completeness, and reliability of information
  • Merchantability and fitness for a particular purpose
  • Non-infringement, where such a disclaimer is legally permitted
  • Compatibility with particular SDKs, packages, platforms, or third-party services
  • Continuous availability or error-free behavior of software and services

Nothing on this page excludes any warranty or legal right that cannot lawfully be excluded.

Use at Your Own Risk

You are responsible for deciding whether to run or adapt code, commands, configurations, infrastructure, integrations, and other material described on this site.

Before You Use an Example

  • Verify: Confirm the relevant API behavior, SDK versions, package versions, and documentation.
  • Test safely: Run unfamiliar commands and software in an isolated development or staging environment before production use.
  • Protect systems and data: Review the impact of commands, permissions, network access, stored data, and third-party tools.
  • Check licenses: Follow the license and other conditions that apply to each source file, library, asset, and dependency.
  • Apply judgment: Obtain qualified assistance for high-impact, commercial, regulated, or security-sensitive applications.

Limitation of Liability

To the maximum extent permitted by applicable law, dotnet-guide.com and its operators disclaim liability for losses or damages arising out of or related to use of this site or its content, including errors or omissions, interrupted access, incompatible or defective code, security incidents, and the actions or availability of third-party services.

This includes, where legally permissible, indirect, incidental, special, consequential, or other damages such as loss of data, revenue, business opportunities, or system availability, even where the possibility of such losses has been communicated.

Nothing in this section is intended to exclude or restrict liability that cannot legally be excluded or restricted.

External Links, Repositories, and Services

We link to official documentation, GitHub repositories, NuGet packages, model providers, cloud platforms, and other websites to help readers verify information or obtain tools. Unless expressly stated otherwise, these destinations are operated independently of dotnet-guide.com.

We do not control third-party availability, licensing, pricing, security, policies, or changes in technical behavior. Review the relevant terms, documentation, and privacy notices before installing software or sharing information with those services.

Copyright, Licenses, and Intellectual Property

Unless otherwise stated, original website text, explanations, design elements, and other original materials are protected by applicable intellectual-property laws. Third-party content and trademarks remain subject to their owners' rights.

Companion Sample Code

Code in our public tutorials GitHub repository is subject to the license published with that repository, except where another notice applies. Check the applicable license file and any third-party notices before copying, modifying, or redistributing code.

Code Appearing in Articles

Where a code snippet displayed in an article is identical to code published under the license in our companion GitHub repository, that license applies to the licensed code regardless of whether it is accessed through the article or the repository, subject to its terms and any applicable third-party notices.

The GitHub repository license does not automatically extend to surrounding editorial text, explanations, commentary, diagrams, screenshots, images, or other website materials unless explicitly stated. These materials remain subject to their respective copyright and licensing terms.

If you are unsure which license or reuse permissions apply to particular content, please review the relevant repository notices or contact us for clarification.

Third-Party Materials

Where we quote, link to, or discuss third-party work, the underlying rights remain with their respective owners. Any reuse must comply with applicable permissions, licenses, and law.

Not Professional or Project-Specific Advice

This website does not provide individualized legal, security, financial, compliance, or professional consulting advice. Its technical content is educational and may not address your particular business, data, infrastructure, contractual, or regulatory obligations.

For critical or commercial deployment decisions, consult appropriately qualified professionals and perform independent engineering, security, compliance, and legal reviews as needed.

User Contributions and Comments

If comments, submissions, or other community contributions are enabled, those materials may reflect the views of their individual authors rather than dotnet-guide.com. We may review, moderate, correct, or remove contributions in accordance with applicable policies and law, but cannot guarantee their accuracy.

Editorial Standards, Corrections, and Feedback

Our Editorial Policy explains how we approach sources, code verification, AI-assisted content, technical reviews, and updates. This disclaimer describes limitations and responsibilities; it does not replace our efforts to publish practical, carefully reviewed educational material.

If you identify an error, outdated command, broken link, or unclear verification claim, please use the contact page. Include the page URL, affected section, relevant versions, and a brief description where possible. We aim to assess reports and make appropriate corrections, but cannot guarantee a particular response time or immediate update.

Changes to This Disclaimer

We may revise this disclaimer as the website, technology, or applicable requirements evolve. Updates will be posted here, and the date at the top of the page will indicate the most recent revision.

Contact Information

For questions about this disclaimer or requests concerning site content, please use our contact page.

Back to Home