Thanks. That resolves the problem. I have copied the files into the same
destination and it works perfectly
Keep up the great work
Ramdas
- Original Message -
From: "Martin Maly" <[EMAIL PROTECTED]>
To: "Discussion of IronPython"
Sent: Friday, September 23, 2005 9:44 PM
Subject: RE:
For the exes to run, they require the IronPython runtime (IronPython.dll
and IronMath.dll). Since we do not install those into the Global
Assembly Cache, running the stand-alone exe in the directory that
doesn't contain Iron*.dll will fail with the message you are seeing.
At this time, generating
IronPython caches COM interfaces it comes across and when the COM object
at hand implements interface that is not in the cache, IP calls method
to convert the COM interface into .NET metadata and that takes a long
time.
Now that you are using the tlbimp-ed version, the interfaces make it to
the cac
I did actually look into this and the join works just fine.
Problem was, if I remember correctly, that we split the file into
different chunks due to newline character handling.
It is definitely semantic difference - and therefore a bug
- so I intend to fix it. It is just that I was focusin
This may be an elementary problem. I tried
searching the list and did not find an answer. When I try creating exe files
from any directory other than /bin, i get this error. How do I create exe files
that I can share with others
Ramdas
Unhandled Exception:
System.IO.FileNotFoundException
Hi
Martin,I just wanted to let you know that this strange bug reported om
Jun 30 is still ocurring:_Hi all,I post this here because I don't know how to describe it in the bug tracker.This simple code re
Please ignore my earlier post about this, I kinda know
what caused the problem now. It seems that when I say
this:
doc = ieApp.Document
IP goes and searches for the type of this thing in the
type library--so it didn't really hang, it just took a
long time for it to find it and return, seemingly.