Strong Names and Enhancing

Thread is closed for posting
2 posts, 0 answers
  1. McKinzie
    McKinzie avatar
    3 posts
    Member since:
    Jul 2009

    Posted 18 Jul 2009 Link to this post


    I'm currently evaluating OpenAccess and I ran across what appears to be a bug or a limitation.  Our application signs the assemblies to give them strong naming.  We use a PFX file (password protected) instead of an SNK (not password protected) to do the signing.  This is all done during compile time via Visual Studio.  This was not using MSBuild (yet).  When I compile the solution after adding an assemble that has been enabled for OpenAccess, I get errors due to those assemblies not being signed.  I also verified in Reflector that they are not signed.  After some searching and experimenting with VEnhance, I tried generating a one off SNK file and signed it with that.  The assembly is now signed correctly.

    Is this a known issue?  Is there a workaround to sign the assembly using a PFX file?

  2. Thomas
    Thomas avatar
    590 posts

    Posted 21 Jul 2009 Link to this post

    Hello Joseph Doyle,

    OpenAccess allows to use .pfx files for signing; I've just re-verified this. The only issue with password protected key files is, that the password must come from somewhere when the solution or project is compiled. For this, the key containers name is passed down to the enhancer with the keyContainer argument.
    Please check that the OpenAccess enhanced assembly's project file is having the right signing settings. When the issue persists, please send us the content of the output window so that we can see what exactly goes wrong.

    the Telerik team

    Instantly find answers to your questions on the newTelerik Support Portal.
    Check out the tipsfor optimizing your support resource searches.
Back to Top