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

Workflow

1. Identify where the application needs stable MIME-type decisions:

- upload validation - download response headers - storage metadata - attachment processing

1. Centralize content-type mapping instead of scattering ad-hoc string tables across the codebase.
2. Use one library boundary for extension and MIME lookups.
3. Validate the extensions and media types that matter to the product.
4. Document any product-specific overrides separately from the library defaults.

Deliver

• guidance on where MIME lookup belongs in application code
• recommendations for centralized content-type decisions
• validation expectations for real file types used by the product

Validate

• MIME mapping is not duplicated across multiple services or controllers
• important file types are verified explicitly
• response or storage code uses the resolved type consistently
• dotnet restore resolves ManagedCode.MimeTypes 10.0.10 or the repository-approved newer version
• focused tests cover known extensions, unknown fallbacks, reverse lookup, upload signature mismatches, and any runtime registrations
• dotnet test passes for the projects that own upload, download, or storage behavior

Related skills