Remove Strong Naming from the Visual Studio Extensibility templates
This suggestion is migrated to Developer Community. Please use below link to view the current status.
Strong naming is a barrier to entry for many new authors of Visual Extensions and provides very marginal value. It requires all the referenced DLLs to be strongly named and the last thing a new extension author wants to be doing is messing around with ildasm.exe.
Developing Visual Studio extensions is hard and the more you can remove these "I have no idea what I'm doing" moments, the better. Signing is an option that (unfortunately) needs to exist but the vast majority of extensions don't need it and it doesn't make sense as a default.
Thanks for the feedback. The updated VSIX project templates in Visual Studio 2019 Preview 3 doesn’t have strong naming.
Visual Studio Extensibility Team
Yann Duran commented
Mads Kristensen even says not to bother signing extensions as it doesn't really serve any purpose or give any benefit..