I am unable to sign my project because FluentValidation.Mvc doesn't have a strong name. You should sign the libraries you publish on NuGet like everyone else otherwise they can't be used in projects with signed assemblies.
Comments: No, the unsigned packages will not be removed. Strong-naming adds additional complexities when it comes to versioning, so this should be something you only opt into if you have a good reason for it. The unsigned will remain the default.
Comments: No, the unsigned packages will not be removed. Strong-naming adds additional complexities when it comes to versioning, so this should be something you only opt into if you have a good reason for it. The unsigned will remain the default.