[IronPython] IronPython 2.7.1 & 3.x Development

Tomas Matousek Tomas.Matousek at microsoft.com
Wed Mar 16 17:40:37 CET 2011

Yes, you can do it and w/o any glue - the version of the assembly is a part of the name, so the assemblies are in fact not named identically. Only the files are and they can be either in GAC or in a different subdirectory of your app. Your App.config can specify subdirectories used to look for assemblies [1]. 

To choose the namespace/class from one assembly or the other use extern aliases [2] in your code.


[1] http://msdn.microsoft.com/en-us/library/823z9h8w(VS.80).aspx
[2] http://www.davidarno.org/c-howtos/aliases-overcoming-name-conflicts-part-2-extern-alias/

-----Original Message-----
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Markus Schaber
Sent: Wednesday, March 16, 2011 12:24 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.7.1 & 3.x Development


Von Tomas Matousek

>>> As I wrote, we host IronPython inside our application, so shebang
>>> file name suffixes are irrelevant - but we could use the shebang as
>>> marker for python 3 (given that we can host both versions
>>> side-by-side) and parse the source manually to find out which
>>> to use - at least for a specific grace period.
>> I think we can support this - it would be no different than using 
>> IronPython and IronRuby side by side, if we do it right. We'd
>> have to rename IronPython.dll to IronPython3.dll as well, but that's
not a
>> big deal.
> The assemblies are strongly named so I don't think that the name
> would be necessary.

Maybe we will need some tricks to solve the reference problems - I don't know whether you can reference two identically named assemblies containing identically named classes from the same C# dll, even if they are signed differently. But I think some kind of glue layer dlls could easily solve that.

Users mailing list
Users at lists.ironpython.com

More information about the Ironpython-users mailing list