Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New comment] AssemblyResolve event in PythonContext may load unnecessary
assemblies
2. [New comment] AssemblyResolve event in PythonContext may load unnecessary
assemblies
----------------------------------------------
ISSUES
1. [New comment] AssemblyResolve event in PythonContext may load unnecessary
assemblies
http://ironpython.codeplex.com/workitem/33313
User jdhardy has commented on the issue:
"Can you post a proposed patch? I'm not exactly sure where you're proposing to
make the change, and if I see it should be able to make a better
decision."-----------------
2. [New comment] AssemblyResolve event in PythonContext may load unnecessary
assemblies
http://ironpython.codeplex.com/workitem/33313
User eldan has commented on the issue:
"In PythonContext.cs file of IronPython project I'm pretty sure it was at line
1379 you have the method that was registered to the AssemblyResolve event. The
problem is this event jumps a lot of times for no reason when I access my
resources in my own code e.g open my form that uses some resources (images)
If you take a look here:
http://connect.microsoft.com/VisualStudio/feedback/details/526836/wpf-appdomain-assemblyresolve-being-called-when-it-shouldnt
specifically this comment:
------------------------------------------------------------------
Posted by ShiverCube on 2/6/2010 at 3:20 AM
The issue is that the AssemblyResolve event has a different behaviour in .NET
4.0 than it does in .NET 3.5. Sure, if you return null in the handler you can
suppress the event, but this doesn't make any sense from an abstraction point
of view. The AssemblyResolve should only be called when a resource cannot be
found, and returning null should throw an Exception (as it does in .NET 3.5).
My main concern is that the even though the behaviour appears to be different
in the new version of .NET, I am unable to find any documentation about the
matter. I would expect that if Microsoft decided to make a radical change such
as this then they would at least have written something about it on MSDN.
------------------------------------------------------------------
That is the problem
What I suggest is when you get the assembly name like MyProgram.resources.dll
or Whatever.resources.dll or any assembly name that ends with .resources
you should ignore it and return null
if (args.Name.EndsWith(".resources.dll")
return null;
"
----------------------------------------------
----------------------------------------------
You are receiving this email because you subscribed to notifications on
CodePlex.
To report a bug, request a feature, or add a comment, visit IronPython Issue
Tracker. You can unsubscribe or change your issue notification settings on
CodePlex.com._______________________________________________
Ironpython-users mailing list
Ironpython-users@python.org
http://mail.python.org/mailman/listinfo/ironpython-users
