Use same signing key between 2013 and 2010
Closed this issue · 1 comments
The 2010 one (v0.4_SP2010 is already in prod) is under GSoft.Dynamite/Properties/GSoft.Dynamite.snk
The 2013 one (ideally, the one we get rid of) is under ~\Shared\GSoft.Dynamite.snk. This may cause problems during ugrapes in environments where Dynamite 2013 is already deployed.
Maybe both are one and the same and we screwed up while linking them to our projects somehow, we'll see...
After review, turns out we were using two different keys. We put the Dynamite-2010 key in /Shared to overwrite the old one. @FranckyC and @yohanb, you can rely on the v0.1_SP2013 release if this causes bad issues. Otherwise, be sure to try retracting fully from any environment where Dynamite-2013 with the old signing key is still present before any upgrade.