Thank you so much!!
Best regards!
Mello
On Mon, May 7, 2012 at 7:21 PM, Jeff Hardy wrote:
> On Mon, May 7, 2012 at 12:34 PM, Cesar Mello wrote:
> > But if I install the MSI instead, how can I reference the standard
> library
> > that is installed with IronPython? Where should I get the standar
On Mon, May 7, 2012 at 12:34 PM, Cesar Mello wrote:
> But if I install the MSI instead, how can I reference the standard library
> that is installed with IronPython? Where should I get the standard library
> path? I tried to get the path from Assembly.GetAssembly(typeof(Python)), but
> the GAC pat
Thanks!
I am evaluating both options.
Installing our own version including the standard library copied from
IronPython (./Lib, ./DLLs) in our application directory seem to work great!
But if I install the MSI instead, how can I reference the standard library
that is installed with IronPython? Wh
On Mon, May 7, 2012 at 7:41 AM, Cesar Mello wrote:
> Hi,
>
> I've noticed IronRuby has merge modules available. Would this be the
> recommended way to redistribute IronPython?
>
> Now I need to embed IronPython in our product's installer. (This is still a
> prototype). Any advices about this? Prob
A colleague of mine also suggested implementing a stand-alone
redistributable, to embed in our product's bootstrapper. That seems to be
an easier trend in our installers. What do you think?
Thanks a lot for the attention.
Best regards
Mello
On Mon, May 7, 2012 at 11:41 AM, Cesar Mello wrote:
>
Hi,
I've noticed IronRuby has merge modules available. Would this be the
recommended way to redistribute IronPython?
Now I need to embed IronPython in our product's installer. (This is still a
prototype). Any advices about this? Probably that's an effort that can be
shared, so instead of developi
