Ivan Porto Carrero wrote:
You could treat it like plugins.
that is have a rubybin folder and a pythonbin folder
Load the correct assemblies in a different appdomain execute your code
there and get the result back.
For Michael this idea isn't new :) I'll that later this week in our
dynamic script control to see how that works out.
Any other more simple and elegant solutions are welcome of course
That sounds like it might work - but it sounds like a complex solution
to a problem that will eventually go away (at least in our case).
What we need effectively are two projects linked to different binaries,
but sharing a single set of core code.
Visual Studio probably doesn't support this as a project structure - but
creating a build script that invokes the compiler to generate two binary
sets from a single source set should be easy enough.
Michael Foord
Cheers
Ivan
On 26/05/2008, at 9:58 AM, Michael Foord wrote:
Hello Ben,
I don't have an answer, just to say that I have the same problem.
For our 'Dynamic Script Control' project we would like to develop
(and test with) for both IronPython and IronRuby.
This makes project structure "problematic".
I realise that at some point this will be a non-problem, but in the
meantime if anyone has any good ideas I'd like to hear them...
Michael Foord
Ben Hall wrote:
Hello,
Posted similar message onto IronRuby but I thought I would also ask
you guys. My scenario is that I need to host IronRuby and IronPython
within the same application. I thought this would be easy as they both
are based on the DLR.
However, you both appear to be at different stages of the DLR life and
building against different sources. Is this the same internally? At
the moment I can't see a way I can build both IronPython and IronRuby
from the same DLR assemblies?
At some point, I take it the DLR will merge into a single release and
known assembly for other language providers and hosts to use instead
of multiple different versions?
In the mean time - what can I do? Is anyone doing this?
Thanks
Ben
Blog.BenHall.me.uk
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
