feat: Please provide signed assemblies in nuget packages

[thomasvanveen]

🙋 Feature Request
Please provide strong-name signed assemblies for the following NuGet packages:

• Microsoft.FluentUI.AspNetCore.Components
• Microsoft.FluentUI.AspNetCore.Components.DataGrid.EntityFrameworkAdapter
• Microsoft.FluentUI.AspNetCore.Components.Icons.Regular
  This would enhance security, eliminate build-time warnings, and ensure package authenticity.

🤔 Expected Behavior
Assemblies included in the above NuGet packages should be signed with a strong name (i.e., have a valid PublicKeyToken). This ensures:

• No CS8002 compiler warnings.
• Ability to use FluentUI Blazor components in strongly signed environments.
• Confidence that the assemblies originate from Microsoft and haven’t been tampered with.

😯 Current Behavior
The referenced assemblies are currently unsigned (PublicKeyToken=null), resulting in:

• Repeated compiler warnings during builds (CS8002).
• Reduced trust for use in security-sensitive applications.
• Potential incompatibility in projects enforcing strong-name validation.

💁 Possible Solution
Publish updated versions of the packages signed with a Microsoft-owned key pair. Ideally:

• Provide signed variants under the same package names and versions (or an updated patch release).
• Optionally offer parallel signed packages to avoid breaking changes for existing consumers.

🔦 Context
We want to use FluentUI Blazor components in an enterprise-grade application with strict assembly verification policies. The lack of strong-name signing:

• Prevents seamless integration.
• Causes persistent build-time warnings.
• Raises legitimate concerns about package integrity and authenticity.
  Manually signing third-party assemblies is not a viable or legally sound workaround.

💻 Examples
CSC : warning CS8002: Referenced assembly "Microsoft.FluentUI.AspNetCore.Components, Version=4.12.1.25197, Culture=neutral, PublicKeyToken=null" does not have a strong name.

This warning appears consistently during builds and affects multiple FluentUI components.

[vnbaaij]

I'm not sure if we are going to be able to do this in the short term. Our project is an open source project and is not owned officially by an engineering team. We have limited resources and I don't know what effort is needed to do this. Will investigate

Confidence that the assemblies originate from Microsoft and haven’t been tampered with.

We DO sign our NuGet packages with an official Microsoft certificate so you can be sure the assemblies come from Microsoft: