Missing Digital Signature in "MahApps.Metro.resources.dll"

[RubavathyImmanuvel]

Bug Description

The "MahApps.Metro.resources.dll" file provided in the MahApps.Metro NuGet package is missing a digital signature. This issue exists in all versions starting from 2.4.0 up to the latest. Furthermore, this is the case for all folders inside the lib directory of the package. The absence of a digital signature can raise concerns in environments where signed assemblies are required for security and compliance.

Steps to reproduce

1. Install any version of the MahApps.Metro NuGet package starting from 2.4.0 (e.g., via Visual Studio or the .NET CLI).
2. Navigate to the lib directory of the installed package.
3. Open the folder for the respective target framework (e.g., netcoreapp3.1 or net5.0) and then "de" folder.
4. Locate the MahApps.Metro.resources.dll file.
5. Right-click on the DLL and open Properties.
6. Check for the Digital Signatures tab in the Properties window----> missing(problem)

Expected behavior

All assemblies distributed in the NuGet package should be digitally signed.

Actual behavior

1. The MahApps.Metro.resources.dll file is not digitally signed.
2. This behavior is observed across all target framework folders inside the lib directory.
3. The issue is present in all versions starting from 2.4.0 to the latest.

Environment

MahApps.Metro version: This issue seems to have started with version 2.4.0, as the MahApps.Metro.resources.dll file was introduced in this version.
Target Framework: All

Screenshots

Proposed solution

Please sign the MahApps.Metro.resources.dll file in future releases to ensure that it complies with security standards. If possible, provide a timeline or guidance for addressing this issue.