[Enhancement] Strong Name assemblies

Summary

Consider strong naming Microsoft.Maui.* and including the snk in the repo.

I understand this wasn’t an option on Xamarin but would this be an option on MAUI?

After all, this is the official library authoring guideline from .NET:

✔️ CONSIDER strong naming your library’s assemblies.

✔️ CONSIDER adding the strong naming key to your source control system.

CSC : error CS8002: Referenced assembly 'Microsoft.Maui, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.

[mattjohnsonpint]

I believe I have found a reasonable workaround:

<PropertyGroup>
  <NoWarn>$(NoWarn);CS8002</NoWarn>
  <SignAssembly>true</SignAssembly>
  <UseMaui>true</UseMaui>
</PropertyGroup>

That allows signed projects to consume unsigned MAUI assemblies. Everything then just works as expected.

[mattjohnsonpint]

Here’s another case for strong naming the MAUI assemblies.

If a MAUI project references a .NET class library that is strong named, the class library won’t be able to use InternalsVisibleTo to make its internals available to the MAUI project. Trying to do so will give a compile error:

[CS1726] Friend assembly reference 'MyMauiAssembly' is invalid. Strong-name signed assemblies must
         specify a public key in their InternalsVisibleTo declarations.