Strong name validation failed for assembly 'Spring.Core'

[Anonymous]

Hi there,

I'm trying to run the examples (moviefinder) and I get the following error:

An unhandled exception of type 'System.IO.FileLoadException' occurred in Unknown Module.

Additional information: Strong name validation failed for assembly 'Spring.Core'.

Any ideas?

thanks

[Aleks Seovic]

Hi Kay,

Problem is that RC2 binaries are not properly signed. You can turn verification off for them by executing "sn -Vr *,65e474d141e25e07" from the command line.

Mark,

We need to either update RC2 with properly signed DLLs or push RC3 out -- this is n-th time people are running into issue with RC2 binaries.

-- Aleks

[Anonymous]

thanks for your quick reply, but I don't see how to run this command,
anyway I will wait for the next RC because I have an old version of spring.net that works good.

PS: thanks for your work

[Mark Pollack]

Hi,

I'm going to work on this today and make an interium release....

Mark

[Mark Pollack]

Hi,

I fixed the build procedure to properly create strongly named assemblies. I will bring the documentation in line with the new support for schema (dropping the dtd) and then make another RC release just to address the strongly named assembly issue. In the meantime, you can download an interium release (with unsigned assemblies) from the download (http://www.springframework.net/download.html) page.

Cheers,
Mark

[Moim]

Hi Mark, I wanted to distribute Spring assemblies along with our application, all our assemblies are strongly named and I am gonna put them into the GAC, now I really want to put the spring.net assemblies into the GAC too. What is the recommendation from you regarding this..?
I can see some dlls that are being used by the Spring.net i.e. antlr.runtime.dll, Common.Logging.dll etc.
These are also have to be strongly named to fit my scenario..right? What is the best approach for me...can I have your kind thoughts on this..?