The COM file in my case was a .dll in the common files directory off
my system root.
Please reference the IronPython tutorial on how to use the .NET SDK
and what it does.
No, it does not decompile a dll into source code.
From my standpoint, it mapped class definitions from my COM file
into .NET and did not eliminate a Windows server running iPy. It just
let me leverage the work with DLR integration by the IronPython team
so I could work in Python.
On Feb 3, 2009, at 1:37 AM, Glauco Uri <[email protected]> wrote:
Rodney Howeedy ha scritto:
FWIW...
I had a client-side COM .dll automation file (used by IE browser)
that connects to a WCOM server running under JBoss on Linux
connecting via JDBC to Oracle on Solaris.
Once we found iPy, we forged ahead with a single Windows host as
the intermediary between our other Unix clients. No .dll COM
automation required on the clients as they all communicate via http
to the single IronPython host running the http server.
The iPy tutorial explains how to convert your .dll COM file using
the .NET SDK and import it for use in IronPython.
This is not clear to me, my COM obj is installed over windows,
with .NET SDK is possible to disassemble and recompile over mono /
linux iron ?
We researched your question about COM on Linux and only found
defunct projects for COM emulation on Unix.
Yes, this is a problem for me, i want to eliminate windows
installation , very espensive to use only fot this COM obj.
But iPy give you the COM automation in your iPy scripts along with
all the Python goodness (e.g. http server, queue server, etc).
yes, i know this solution, if i cannot found any solution for
migrating in one linux server.
Thank you
Glauco
_______________________________________________
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
