Certificate signing isn’t a perfect answer for untrusted code, but it does give the user another indication that your Add-In will do what it says on the tin. More importantly, not signing your code when the installer framework expects a certificate isn’t a great way to make a first impression. Not cool. Previously, we talked about automating builds of our Add-In’s installers and the parent *.wssx add-in package file, and my strategy for automatically building packages that support in-place upgrades. Now we’re going to talk about signing our *.wssx package with a certificate, specifically a...