Author Topic: Strong name signature not valid for wcl.dll  (Read 4719 times)

Offline mschulze

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Strong name signature not valid for wcl.dll
« on: December 12, 2011, 10:57:40 PM »
I am trying to deploy an application with WCL for .NET using Click Once, and after installation appears to complete, I get an "Application validation did not succeed" error.  The specific error appears to be "Strong name signature not valid for this assembly wcl.dll."  This is using .NET 4.0 and VS 2010.  Originally I had an error (probably the same one) trying to deploy for .NET 2.0 using VS 2005 - the detailed error message there was "The manifest XML signature is not valid."

I've double-checked all the references to the DLLs and all their properties and made sure to target 32-bit CPU and tried a whole bunch of other things I can't even remember now, always with the same result.

Any help greatly appreciated.

Thanks!
Mark

Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3052
  • Karma: 1000
    • Soft Service Company
Re: Strong name signature not valid for wcl.dll
« Reply #1 on: December 13, 2011, 06:39:05 AM »
Hello,

What VCL version do you use?

Offline mschulze

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Strong name signature not valid for wcl.dll
« Reply #2 on: December 13, 2011, 05:16:30 PM »
WCL version is 6.8.1.0.

Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3052
  • Karma: 1000
    • Soft Service Company
Re: Strong name signature not valid for wcl.dll
« Reply #3 on: December 13, 2011, 05:31:30 PM »
Please, update to the latest version. The issue with strong name has been fixed in 6.9.0.0: http://www.btframework.com/news.htm#a06032011

Offline mschulze

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Strong name signature not valid for wcl.dll
« Reply #4 on: December 13, 2011, 05:49:48 PM »
I don't really want to have to buy a whole new license just to get this working.  Is there really no other way?

Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3052
  • Karma: 1000
    • Soft Service Company
Re: Strong name signature not valid for wcl.dll
« Reply #5 on: December 13, 2011, 06:38:53 PM »
try to resign it with sn.exe.

Offline mschulze

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Strong name signature not valid for wcl.dll
« Reply #6 on: December 13, 2011, 09:42:15 PM »
I tried re-signing with sn.exe but without the ability to compile the source, sn.exe cannot sign the assembly.  Next I tried the instructions here:

http://ryanfarley.com/blog/archive/2010/04/23/sign-a-.net-assembly-with-a-strong-name-without-recompiling.aspx

to disassemble the assembly and reassemble it with a new signature but that also failed.  (The ilasm.exe tool reports "***** FAILURE *****" after assembling many methods, right after assembling SingletonDomainUnload.)

Now I have tried dropping back to .NET 3.5 (VS 2010) and deployment fails at the same point, but this time it reports "Manifest XML signature is not valid" - exactly as it did when using the library with VS 2005 and .NET 2.0.

Is it possible to deploy an application using WCL 6.8.1.0 or must I upgrade in order for it to work?

Thanks!

Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3052
  • Karma: 1000
    • Soft Service Company
Re: Strong name signature not valid for wcl.dll
« Reply #7 on: December 13, 2011, 09:52:24 PM »
The problem was that VS 2010 can't sign assembly when build it. So assembly for .NET 4.0 is partial signed in WCL before 6.9. Unfortunately a key file is available in WCL with sources version only. But if you send me your wcl.dll (to mike@btframework.com) for VS 2010 (.NET 4.0) I can sign it here and send you back.

Offline mschulze

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Strong name signature not valid for wcl.dll
« Reply #8 on: December 13, 2011, 10:48:53 PM »
Thank you Mike!  The signed copy of the DLL seems to have solved the problem.

 

Sitemap 1 2 3 4 5 6 7 8 9