Hi, Thomas, I did know about the assembly version being part of the name, but I did not know yet about the extern aliases. I'm learning something new every day...
Thanks a lot! Best regards Markus Schaber ___________________________ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber | Developer Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50 Email: m.scha...@3s-software.com | Web: http://www.3s-software.com CoDeSys internet forum: http://forum.3s-software.com Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915 > -----Ursprüngliche Nachricht----- > Von: users-boun...@lists.ironpython.com [mailto:users- > boun...@lists.ironpython.com] Im Auftrag von Tomas Matousek > Gesendet: Mittwoch, 16. März 2011 17:41 > An: Discussion of IronPython > Betreff: Re: [IronPython] IronPython 2.7.1 & 3.x Development > > 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. > > Tomas > > [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-boun...@lists.ironpython.com [mailto:users- > boun...@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 > > Hi, > > Von Tomas Matousek > > >>> As I wrote, we host IronPython inside our application, so shebang > and > >>> file name suffixes are irrelevant - but we could use the shebang as > a > >>> marker for python 3 (given that we can host both versions > >>> side-by-side) and parse the source manually to find out which > version > >>> 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 > probably > >> 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 > change > > 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. > > Thanks, > Markus > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > > > > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
