views:

70

answers:

2

I have a solution with about 10 projects, and I recently upgraded to new version on NHibernate, yet when I run solution and get the message: "The located assembly's manifest definition does not match the assembly reference". So some component is looking for old version. I tried removing all references in my project to NH, and re-adding them, deleting all bins etc. I know I can redirect in the config file to a new version, but none of the projects should be depending on the old version. So is there a way to find out which dll is dependent on an old version?

+2  A: 

Reflector can help with this - load the assembly and view the entries under "References".

Andrew Hare
Ahhh, how I did not think of that. Anyway none of the dll depend on the old one, according to reflector. Hmmm, there must be something else going on. I inspected every dll in the bin.
epitka
+3  A: 

There's also Dependency Walker.

DaveE