Overview of DiagConfig tool
main.editorconfig files that control diagnostic messages for different types of source code (e.g., production, test, or benchmark code).repository·main·Indexed 25 days ago
https://github.com/dotnet/extensionsA collection of libraries and tools providing enriched capabilities for production-ready .NET applications. It focuses on AI, resilience, telemetry, compliance, and diagnostics, and includes tools like ApiChief for API surface analysis, DiagConfig for managing diagnostic configuration YAML files, and DiagPublisher for diagnostic ID management. The repository also provides legacy support polyfills and injections for older frameworks to enable modern C# features and APIs.
.editorconfig files that control diagnostic messages for different types of source code (e.g., production, test, or benchmark code).The Microsoft.Extensions.AI.Evaluation ecosystem consists of several specialized packages:
dotnet/extensions repository provides a suite of libraries designed for building production-ready, high-scale, and high-availability applications. These libraries extend standard .NET functionality to improve efficiency, robustness, and manageability across several functional areas.Microsoft.Extensions.ServiceDiscovery.Abstractions library defines the core interfaces and types used for service discovery within the .NET ecosystem. It serves as the foundation for the Microsoft.Extensions.ServiceDiscovery implementation and allows other libraries to implement custom service discovery extensions, such as service endpoint providers.This library measures and reports processor and memory usage. It provides platform-specific monitoring implementations:
The Microsoft.Extensions.VectorData.Abstractions package provides a standardized set of abstract classes and utilities for interacting with vector databases. It allows developers to write code that is decoupled from specific database implementations.
Key capabilities provided by these abstractions include:
Microsoft.Extensions.AI.The Microsoft.Extensions.AI.Evaluation libraries are a set of .NET packages designed to support building processes for evaluating the quality and safety of AI software. The ecosystem is divided into several specialized packages:
Microsoft.Extensions.AI.Evaluation: Core abstractions and types.Microsoft.Extensions.AI.Evaluation.Quality: Evaluators for response quality (e.g., Relevance, Truth, Completeness, Fluency, Coherence, Retrieval, Equivalence, and Groundedness).Microsoft.Extensions.AI.Evaluation.Safety: Evaluators built on Azure AI Foundry Evaluation service for content safety (e.g., Protected Material, Groundedness Pro, Ungrounded Attributes, Hate and Unfairness, Self Harm, Violence, Sexual, Code Vulnerability, and Indirect Attack).Microsoft.Extensions.AI.Evaluation.NLP: Evaluators for NLP and machine translation tasks (e.g., BLEU, GLEU, and F1 scores).Microsoft.Extensions.AI.Evaluation.Reporting: Support for caching LLM responses, storing evaluation results, and generating reports.Microsoft.Extensions.AI.Evaluation.Reporting.Azure: Azure Storage implementation for caching and storing evaluation results.Microsoft.Extensions.AI.Evaluation.Console: A command-line tool for managing evaluation data and generating reports.The Microsoft.Extensions.Caching.Hybrid package provides a concrete implementation of the HybridCache API. It is designed to simplify and enhance cache usage by encapsulating serialization and cache management details.
Key features include:
IDistributedCache: Works immediately with existing backends like Redis, SQL Server, and CosmosDB.IBufferDistributedCache API.DiagPublisher tool is used to generate or update diagnostic IDs. These IDs are used to maintain the list of diagnostics documented in /docs/list-of-diagnostics.md.HybridCache implementation provides a unified way to handle serialization, caching, and stampede protection. It is designed to prevent redundant backend operations when multiple callers request the same key simultaneously.Microsoft.McpServer.ProjectTemplates package provides project templates specifically designed for creating Model Context Protocol (MCP) Servers. These templates help developers quickly bootstrap new MCP Server projects with the necessary structure and dependencies.The Microsoft.Extensions.AmbientMetadata.Build provider allows applications to access build-time metadata (such as CI/CD environment variables) during runtime. It specifically targets variables provided by build systems like Azure DevOps and GitHub Actions.
To use this, ensure your build environment provides the standard environment variables defined by your CI provider: