-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AssemblyManager.GetAssemblyByFile might have a bug #21
Comments
And the weird thing is, after I run with new tool. Check the dependency correctly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/s-siplivy/PackageChecker/blob/master/PackageChecker/PackageChecker/Files/AssemblyManager.cs#L15
Today I encounter a problem, this tool could not recognize the assembly version of physical file.
A.dll depends on B.dll, and both of them locate on same bin folder of a mvc site.
A.dll requires B.dll with version 1.1.1, and the assembly version of B is correct(1.1.1) under bin folder.
However this tool gives info, that A.dll requires B.dll with another version 1.1.0.
It seems, A.dll is not correct loaded.
I replace the method content with
https://stackoverflow.com/questions/49283983/getting-wrong-version-from-assembly-using-reflection
There are lots of load related methods under Assembly https://docs.microsoft.com/en-us/dotnet/api/system.reflection.assembly.createinstance?view=net-5.0
Not sure which is the most correct one to use
The text was updated successfully, but these errors were encountered: