When adding MimeTypes to a .net standard 2.0 Project, Compile Error:

CS8370 "Feature 'nullable reference types' is not available in C# 7.3. Please use language version 8.0 or greater"

.net Standard 2.0 is unfortunately locked to max language level 7.3

Using Version 1.1.0 , which does not yet have the
#nullable enable
line works.

Hi @khellang -
I am the new maintainer of:
https://www.nuget.org/packages/Mime-Detective/
https://github.com/MediatedCommunications/Mime-Detective

and have recently published an update expanding to over 14,000 mime signatures. Are you open to combining/joining efforts?
If so, can you add TonyValenti as a admin on the MimeTypes nuget package?

Because you are using namespace $rootnamespace$ I currently cannot enable XML documentation in combination with treat warnings as errors. Since some things aren't commented.

Would it be possible to either add comments or change the namespace?

My problem as I get mimetype from email and sometimes it's broken.

If empty i use detection from filename otherwise if it's not empty I want to validate it

It would be nice that this module supports DNX, so it can be used from CoreCLR assemblies.

Independent of the file extensions, this library always returns application/x-cbr. This is incorrect, as there are specific MIME types for all the extensions, e.g. application/x-cbz or application/x-cb7.

To understand the impact, see the following issues in the Jellyfin project:

• jellyfin/jellyfin-plugin-opds#38 and
• jellyfin/jellyfin#11009

.

Here's a tl;dr: cbr (a.k.a. Rar) is a proprietary compression algorithm, so most FOSS eReaders will not accept it. 🙂

Allow to lookup the extension based on the MimeType please.

If method signature allows null string, why it throws exception?

Hi,

Any chance the jfif extension could be added to the typeMap?
I believe it just has the mime type of image/jpeg.

Thanks!

There is a NuGet package released with version 2.4.1 uploaded on 2023-02-21: https://www.nuget.org/packages/MimeTypes/2.4.1. It was released by Kristian Hellang, the owner of this Repository.

As of today, this repository does not contain a tag for version 2.4.1, no commits in 2023 and the code released is different from the code in this repository: Compare MimeTypes.cs.pp in this repo with contentFiles/cs/*/MimeTypes.cs.pp in Release 2.4.1.

The differences between the code released and the code in this repository are not backwards compatible. E.g. getting the MIME type for a file with ".mp4" extension returns "application/mp4" in v2.4.1 instead of "video/mp4".

What is up with this?

Hello,

I've tried using this library in a Xamarin.mac project but got the following error.
Is it normal?

Could not install package 'MimeTypes 2.4.0'. You are trying to install this package into a project that targets 'Xamarin.Mac,Version=v2.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

There are duplicates on some of the extensions which fails the initialization of the dictionary:
( 'sub', 'image/vnd.dvb.subtitle' ),
( 'sub', 'text/vnd.dvb.subtitle' ),

and

( 'wmz', 'application/x-ms-wmz' ),
( 'wmz', 'application/x-msmetafile' ),

Hi,

In version 2.4.0 MP4 MIME type was correctly returning video/mp4 but in 2.4.1 it returns application/mp4.

If an MP4 file contains video the MIME type should be video/mp4. If it is a file with just e.g. subtitles or metadata, then application/mp4 would be correct. Is the video/mp4 option not the more common file?

https://developer.mozilla.org/en-US/docs/Web/Media/Formats/codecs_parameter

When the NuGet package is added to a .NET Core project, the MimeTypes.cs file does not get generated or added to the project.

Hello,

I try to use this package in Xamarin.Android, but I get build errors because of namespace issues.

If I edit the code file manually like this. it works:

I just prepended all the using statements at the top with "global::"

Another fix which works for me is moving the using statements out of the namespace declaration, like so:

If you could fix this one way or another, that would be awesome!

Regards,
labtox