Report assemblies which exist in an incorrect version

[agross]

For an executable that references a custom strong-named assembly that is only available in an incorrect version, report the reference.

[mikehadlow]

Yes, that would be very nice. Would you care to take a look at the code and see if you can implement it. I'd welcome a pull request.

[agross]

This is as far as I got: agross/AsmSpy@24176b40eddc3db9378d79eff33eef4d306c26c0

What I found interesting that I got several FileNotFoundExceptions for the directory I tested against, although the assemblies in question are readable.

I'd appreciate a review.

[mikehadlow]

Hi Alexander,
Very busy at the moment, but I'll try to get around to it if possible.
Thanks
Mike

On Mon, Nov 4, 2013 at 2:14 PM, Alexander Groß [email protected]:

This is as far as I got: agross/AsmSpy@24176b4https://github.com/agross/AsmSpy/commit/24176b40eddc3db9378d79eff33eef4d306c26c0

What I found interesting that I got several FileNotFoundExceptions for
the directory I tested against, although the assemblies in question are
readable.

I'd appreciate a review.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-27687340
.

[rahulpnath]

@agross If you still remember what this is :)
Does this also not depend on the assembly binding redirects? So it is still be valid to have a different version in the references than that is present in the bin/application directory

[agross]

AFAIR we didn't have binding redirects in the tested directory.

[agross]

I think I remember that the reason we were looking at AsmSpy at that time was that our application didn't run, despite all assemblies being correct. Or so we thought. I created the issue because of this as displaying version mismatches would have helped us identifying the culprit (wrong assembly version in bin directory) faster.

[rahulpnath]

Cool thanks @agross for confirming. But The fix for this will need to check assembly binding entries too and not just the assembly version that an exe refers too. @mikehadlow Any thoughts on this?