Make NuGet assemblies strongly-named

Not sure whether previous versions were strongly-named. If no, consider this a feature request, otherwise a bug report.

[JakeGinnivan]

VSTO Contrib has never been strong named, mainly because of the pain that can be involved. I want to release v1 over the next week or so, and I will be adopting SemVer then, so I will do strong naming then (not that I am a fan of strong naming in general :P)

When there is no strong name it cannot be used from any strongly-named
assemblies (unless we compile it ourselves from sources, which we are doing
so far).

2013/11/27 Jake Ginnivan notifications@github.com

VSTO Contrib has never been strong named, mainly because of the pain that
can be involved. I want to release v1 over the next week or so, and I will
be adopting SemVer then, so I will do strong naming then (not that I am a
fan of strong naming in general :P)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/29#issuecomment-29395535
.

[JakeGinnivan]

I actually might strong name v1, because Office add-ins share an appdomain it is a good idea