.net version display in file properties for libMBIN

[Babscoole]

Is your feature request related to a problem? Please describe.
Although each .net version of libMBIN is built with a different filename, (libMBIN.dll for .net 5, libMBIN-dotnet6.dll for .net 6, and libMBIN-dotnet4.dll for .net 4), each program that utilizes and is packaged with libMBIN requires the file name to be libMBIN.dll. Makes it difficult to determine which .net version is being used by any given application.

Describe the solution you'd like
When viewing libMBIN file properties, should be labeled which .net version it is, either in the Product name or File description fields.

Additional context

[Kobi-Blade]

For .NET libraries, the target framework is already in the assembly metadata and can be read via GetCustomAttribute<TargetFrameworkAttribute>().

Adding the framework to file properties is redundant.

[monkeyman192]

I guess the reason is because many people won't be using libMBIN.dll directly, so this would be for those who are just using the actual MBINCompiler.exe

[Kobi-Blade]

I guess the reason is because many people won't be using libMBIN.dll directly, so this would be for those who are just using the actual MBINCompiler.exe

I just trying to understand what is the issue here, OP said,

each program that utilizes and is packaged with libMBIN requires the file name to be libMBIN.dll. Makes it difficult to determine which .net version is being used by any given application

Developers who need to verify which version is being used for whatever reason, can inspect the metadata directly and add a check in their code.

Plus, the specific .NET version in use is largely irrelevant, as the library features and codebase remain consistent across versions, the only difference lies in the runtime.