On 6/29/2011 10:48 AM, Dave Peterson wrote:
But I'm confused. Doesn't the fact that a C# app loads the assembly just fine
mean that the CLR can load it ok?
Not necessarily. This is a complicated topic in .NET development, and is
beyond what I can bang out in a quick email.
Here are some links that you might find helpful:
"How the Runtime Locates Assemblies"
http://msdn.microsoft.com/en-us/library/yx7xezcf.aspx
"Tips for debugging assembly load/bind errors, strong name problems, and
manual IL code changes"
http://social.msdn.microsoft.com/Forums/en/clr/thread/4cbff9e8-758e-4c0c-9997-2e656f3eb22d
And given that fuslogw is part of VS or Win SDK, I'm thinking it won't help
with figuring out why ipy.exe won't.
Then again, I can't explain why ipy would be doing anything special to
load an assembly either, so it can't hurt to try this tool.
ipy runs on the CLR, so the CLR is responsible for loading assemblies.
fusionlogw allows you to get more information about all CLR binding
errors (i.e. assembly load errors) on a machine, so it works with ipy.
_______________________________________________
Ironpython-users mailing list
Ironpython-users@python.org
http://mail.python.org/mailman/listinfo/ironpython-users
