I suggest you ...

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.
https://developercommunity.visualstudio.com/content/idea/351462/remove-strong-naming-from-the-visual-studio-extens.html
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.

15 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Josh Varty shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Yann Duran commented  ·   ·  Flag as inappropriate

    Mads Kristensen even says not to bother signing extensions as it doesn't really serve any purpose or give any benefit..

Feedback and Knowledge Base