This project has moved and is read-only. For the latest updates, please go here.

Binary download : assembly not strong named

Oct 4, 2011 at 3:07 PM
Edited Oct 4, 2011 at 3:33 PM

Hi, in the binary download of the TaskScheduler assembly, the assembly is not signed.  Probably it is a good idea distribute it as a strong named assembly.

Also, the source code contains a (the ?) signing key file.

So, for now I made a compilation of my own and signed it with this key, but I believe you better make available a signed binary.


Joris Spriet

Oct 4, 2011 at 7:53 PM

Thank you for your suggestion. The reason the key is there is specifically so it can be compiled and signed by those that need it. When I released it a couple of years ago signed, I had some big backlash from the community.

Oct 4, 2011 at 7:57 PM

If you can elaborate I would like to know what requirements you have for strongly named assemblies so I can make a more informed decision. Also, what problems have you run into with strongly named assemblies in the past and how have you worked around them?

Oct 5, 2011 at 12:48 AM

At my company, we sign all our assemblies.  It serves as a sign to our customers the assembly can be trusted - and it was produced on our build server.

As a consequence, we only can use third-party assemblies that are signed as well.  If a third-party component is not available signed,

we basically don't use it.  For TaskScheduler, as the source contained a snk, I compiled and signed it myself.

The library was just what I needed, and, okay, so I cheated here, but that is why I posted this remark...