[Ironpython-users] IronPython, Daily Digest 9/2/2011

no_reply at codeplex.com no_reply at codeplex.com
Sat Sep 3 13:38:03 CEST 2011

Hi ironpython,

Here's your Daily Digest of new issues for project "IronPython".

In today's digest:ISSUES

1. [New issue] Better handling of binding failure due to .Net version



1. [New issue] Better handling of binding failure due to .Net version
User skottmckay has proposed the issue:

"The error message if binding of an assembly fails (clr.AddReference et al) is woefully unhelpful if the failure is due to attempting to load an assembly from a different clr version. I recently had this problem attempting to load a .net 2 assembly with .net 4 iron python. 

Some options:

1) Is there any reason why IronPython couldn't be shipped with an app.config file with the following to allow loading of .net 2 assemblies in .net 4, or at least information added to the FAQ for the user to create this file themselves (of course they will probably need a better error message to point them in the right direction first).

<?xml version="1.0" encoding="utf-8" ?> 
  <startup useLegacyV2RuntimeActivationPolicy="true"> 
            <supportedRuntime version="v4.0" />    

2) Could code be added to detect a mismatch and provide the user with a meaningful error message. For example, here are the steps to get the clr version from a dll.

>>> import clr
>>> import System
>>> asm = System.Reflection.Assembly.ReflectionOnlyLoadFrom("my.dll")
>>> print asm.ImageRuntimeVersion

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20110903/3f0a9d69/attachment.html>

More information about the Ironpython-users mailing list