managedcode-mimetypes

# ManagedCode.MimeTypes ## Trigger On - integrating `ManagedCode.MimeTypes` into upload or download flows - mapping file extensions to content types in APIs or background processing - reviewing content-type handling for files, blobs, or attachments - documenting a reusable MIME-type decision point in a .NET application ## Install ```bash dotnet add package ManagedCode.MimeTypes --version 10.0.9 ``` Use `PackageReference` when the repository centralizes dependency versions: ```xml <PackageReference Include="ManagedCode.MimeTypes" Version="10.0.9" /> ``` The current package targets .NET 8, 9, and 10. Keep the version in the repository's existing central package-management file when one is present. ## Workflow 1. Identify where the application needs stable MIME-type decisions: - upload validation - download response headers - storage metadata - attachment processing 2. Centralize content-type mapping instead of scattering ad-hoc string tables across the codebase. 3. Use one library boundary for extension and MIME lookups. 4. Validate the extensions and media types that matter to the product. 5. Document any product-specific overrides separately from the library defaults. ## Read MIME Metadata Map file names, URLs, and compound extensions through the generated catalog: ```csharp using ManagedCode.MimeTypes; var reportType = MimeHelper.GetMimeType("report.pdf"); var archiveType = MimeHelper.GetMimeType("archive.tar.gz"); var imageType = MimeHelper.GetMimeT...