FileLoadException

[Berryl Hesh]

Goal:
Use an example project I found which illustrates use of design patterns that
facilitate unit testing, so I can incorporate these patterns into my own
projects. One pattern is built on NHibernate. The dll for nhibernate which
came with the project was version v1.1.4322, as the sample code is almost a
year old. The NHibernate dll I downloaded is v2.0.50727.

Problem(s):
* I could not get this one project of several to complile, so I started to
migrate the entire solution to a new solution using updated versions of the
dependent dlls, like NHibernate.This worked well for several dependent
projects I needed to compile and test prior to this one.
* After migrating this sub-project to my new solution builds fine, but when
I run a test that uses NHibernate, I get:
"Could not load file or assembly 'NHibernate, Version=1.2.0.4000,
Culture=neutral, PublicKeyToken=aa95f207798dfdb4' or one of its
dependencies. The located assembly's manifest definition does not match the
assembly reference."

How can I fix this??

Why is my test looking for v1.2 in the first place. The reference dll it's
built on s/n 2.0. I looked in the GAC but didn't see any NHibernate
assemblies there.

Thanks for any help! BH

[Jon Skeet [C# MVP]]

Berryl Hesh <ef******@yahoo.comwrote:

Goal:
Use an example project I found which illustrates use of design patterns that
facilitate unit testing, so I can incorporate these patterns into my own
projects. One pattern is built on NHibernate. The dll for nhibernate which
came with the project was version v1.1.4322, as the sample code is almost a
year old. The NHibernate dll I downloaded is v2.0.50727.

Those sound very unlikely numbers - they are the version numbers of the
..NET framework itself. It's unlikely that NHibernate just happened to
use the same minor version numbers.

Problem(s):
* I could not get this one project of several to complile, so I started to
migrate the entire solution to a new solution using updated versions of the
dependent dlls, like NHibernate.This worked well for several dependent
projects I needed to compile and test prior to this one.
* After migrating this sub-project to my new solution builds fine, but when
I run a test that uses NHibernate, I get:
"Could not load file or assembly 'NHibernate, Version=1.2.0.4000,
Culture=neutral, PublicKeyToken=aa95f207798dfdb4' or one of its
dependencies. The located assembly's manifest definition does not match the
assembly reference."

How can I fix this??

Why is my test looking for v1.2 in the first place. The reference dll it's
built on s/n 2.0. I looked in the GAC but didn't see any NHibernate
assemblies there.

Not sure what you mean by "s/n" there.

--
Jon Skeet - <sk***@pobox.com>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com

[Berryl Hesh]

You're right about the numbers being CLR versions. The version of NHibernate
refernce in the project is 2.0.0.4000. My question is where is the old
version 1.2.0.4000 in the error message is coming from?
"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:MP*********************@msnews.microsoft.com. ..

Berryl Hesh <ef******@yahoo.comwrote:

>Goal:
Use an example project I found which illustrates use of design patterns
that
facilitate unit testing, so I can incorporate these patterns into my own
projects. One pattern is built on NHibernate. The dll for nhibernate
which
came with the project was version v1.1.4322, as the sample code is almost
a
year old. The NHibernate dll I downloaded is v2.0.50727.

Those sound very unlikely numbers - they are the version numbers of the
.NET framework itself. It's unlikely that NHibernate just happened to
use the same minor version numbers.

>Problem(s):
* I could not get this one project of several to complile, so I started
to
migrate the entire solution to a new solution using updated versions of
the
dependent dlls, like NHibernate.This worked well for several dependent
projects I needed to compile and test prior to this one.
* After migrating this sub-project to my new solution builds fine, but
when
I run a test that uses NHibernate, I get:
"Could not load file or assembly 'NHibernate, Version=1.2.0.4000,
Culture=neutral, PublicKeyToken=aa95f207798dfdb4' or one of its
dependencies. The located assembly's manifest definition does not match
the
assembly reference."

How can I fix this??

Why is my test looking for v1.2 in the first place. The reference dll
it's
built on s/n 2.0. I looked in the GAC but didn't see any NHibernate
assemblies there.

Not sure what you mean by "s/n" there.

--
Jon Skeet - <sk***@pobox.com>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com

[Jon Skeet [C# MVP]]

Berryl Hesh <ef******@yahoo.comwrote:

You're right about the numbers being CLR versions. The version of NHibernate
refernce in the project is 2.0.0.4000. My question is where is the old
version 1.2.0.4000 in the error message is coming from?

That does seem odd. What does the stack trace look like? That might
show what's expecting 1.2.0.4000. The fact that the "4000" is the same
in both cases is somewhat suspicious.

--
Jon Skeet - <sk***@pobox.com>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com

[Jon Skeet [C# MVP]]

Berryl Hesh <ef******@yahoo.comwrote:

(Exception from HRESULT: 0x80131040)

I am thinking it's some configuration type of problem. I get the same error
if I exclude the config file that came with the code, and the code near the
start of the error is trying to load that file too.

Okay, I suggest you have a look at the Castle DLLs to see whether they
reference v1.2.0.4000. That looks like the most likely candidate.

The other thing that you can do is turn on the fusion log (search for
details) which I *think* explains why assemblies are loaded.

--
Jon Skeet - <sk***@pobox.com>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com

[Berryl Hesh]

Using ildasm I can see in Castle.ActiveRecord's manifest the explanation for
the error:
.assembly extern NHibernate
{
.publickeytoken = (AA 95 F2 07 79 8D FD B4 ) // ....y...
.ver 1:2:0:4000
}

It seems like a pretty popular solution, so I'm surprised there isn't a
build incorporation NHibernate's newest release, or even some mention of it.
So now I have to decide whether to use the older NHibernate dll (this sounds
confusing if ever the newer one's features become desireable), or try to
make an ActiveRecord build myself with the new NHibernate (sounds like
trouble, and if it were easy I would find it somewhere

Thanks again for your help - BH

"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:MP*********************@msnews.microsoft.com. ..

Berryl Hesh <ef******@yahoo.comwrote:

>(Exception from HRESULT: 0x80131040)

I am thinking it's some configuration type of problem. I get the same
error
if I exclude the config file that came with the code, and the code near
the
start of the error is trying to load that file too.

Okay, I suggest you have a look at the Castle DLLs to see whether they
reference v1.2.0.4000. That looks like the most likely candidate.

The other thing that you can do is turn on the fusion log (search for
details) which I *think* explains why assemblies are loaded.

--
Jon Skeet - <sk***@pobox.com>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com