Signing a 3rd party assembly

Last night a blog post saved my life….

We wrote some tests, wrote some code. Red, green refactor. There were regular expressions, they passed first time! All was beautiful. Then we moved the code out of the tests into the main project and it all went wrong. The project we moved it to was strongly typed, the 3rd party dll we referenced wasn’t. We despaired. We tried getting the source of the 3rd party assembly, sign it, recompile, but alas the latest source was using .NET 4 and wasn’t compatible. Then we found this amazing post. It’s clear, succint and, like a Deliah Smith Recipe, it works.

Here it is in all its glory. Enjoy. Thank you @thecolonial

http://buffered.io/2008/07/09/net-fu-signing-an-unsigned-assembly-without-delay-signing/

One thought on “Signing a 3rd party assembly

  1. Hey ruby_gem,

    It’s posts like this that keep me blogging 🙂 I’m very happy to hear that my post helped you solve the problem.

    It’s incredibly frustrating when you are given DLLs from a third-party that aren’t signed. Not only is it an indication of a lack of care/professionalism on their behalf, it also shows that the third-party isn’t really aware of issues that they’re opening themselves up to. If you’re releasing libraries to other developers, sign them! It’s that simple.

    At least we have a solution though eh?

    All the best to you and good luck with your projects.

    OJ 🙂

What did you think?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s