2006/6/16, jeff sacksteder <[EMAIL PROTECTED]>:
>
> That appears to still create a console window at runtime. Can that be
> disabled? I know that Py2exe can create 'console' or 'windows' applications
> optionally.
This is the issue #346 and it seems that it will be fixed in 1.0 Beta 8.
http://www
And this will produce a source.exe file. The executable, however, willstill need the
IronPython.dll reference.That appears to still create a console window at runtime. Can that be disabled? I know that Py2exe can create 'console' or 'windows' applications optionally.
___
What is the plan regarding "News Feeds" tab of IronPython homepage on CodePlex?
It could aggregate Jim Hugunin's blog and other IronPython crew blogs,
for example.
http://blogs.msdn.com/hugunin/
An example of "News Feeds" tab in action:
http://www.codeplex.com/Project/NewsFeeds.aspx?ProjectName=C
It could also help to use Fuslogvw.exe to watch the binding failure --
http://msdn2.microsoft.com/en-us/library/e74a18c4.aspx
At 08:16 PM 6/14/2006, Dino Viehland wrote
>Are you remoting to another process, or to another app domain? Does the other
>process have access to IronPython.dll ?
>
>One
To compile a Python source file to an executable, you can use the
X:SaveAssemblies option in the IronPython console.
Given a file source.py, you would just do:
IronPythonConsole X:SaveAssemblies source.py
And this will produce a source.exe file. The executable, however, will
still need the
Ok, I've looked into this some more now... Turns out that all my previous
advice was useless.
The problem here is actually that MarshalByRefObject's will happily cast to any
interface you ask for. For example in C# if you try and cast some random MBR
to IComparable, it works. Only when you c
I am using a seperate process. After I include IronPython.dll in the library
where my remote object is implemented, I get the following exception:
"Attempted to call a method declared on type
'IronPython.Runtime.IDynamicObject' on an object which exposes
'RemotingServerClient.ServerTalk'." (Remo
