Thanks!<div><br></div><div>I am evaluating both options.</div><div><br></div><div>Installing our own version including the standard library copied from IronPython (./Lib, ./DLLs) in our application directory seem to work great!</div>
<div><br></div><div>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 path is returned instead of C:\Program Files (x86)\IronPython 2.7.</div>
<div><br></div><div>Thank you a lot for the attention!</div><div><br></div><div>Best regards</div><div>Mello</div><div><br></div><div><br></div><div><br><div class="gmail_quote">On Mon, May 7, 2012 at 12:46 PM, Jeff Hardy <span dir="ltr"><<a href="mailto:jdhardy@gmail.com" target="_blank">jdhardy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mon, May 7, 2012 at 7:41 AM, Cesar Mello <<a href="mailto:cmello@gmail.com">cmello@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> I've noticed IronRuby has merge modules available. Would this be the<br>
> recommended way to redistribute IronPython?<br>
><br>
> Now I need to embed IronPython in our product's installer. (This is still a<br>
> prototype). Any advices about this? Probably that's an effort that can be<br>
> shared, so instead of developing proprietary installation components I may<br>
> contribute work on generic merge modules.<br>
<br>
</div>If you've already got a bootstrapper, I would just but IronPython's<br>
MSI in there. Merge modules are really fragile and tend to break in<br>
weird ways, so I don't build them for IronPython (I refactored IP's<br>
MSI builds, so that's why they're different from IR's). The<br>
recommendation from MS seems to be to use full MSIs and chain them<br>
using a bootstrapper.<br>
<br>
One thing to watch for is that a user could upgrade IP and cause your<br>
app to be running against a new version. I try to make sure that<br>
upgrades shouldn't break anything for just that reason, but it does<br>
happen. The only way around this would be to build IP yourself, with a<br>
different signing key or AssemblyVersion, and ship that version with<br>
your app.<br>
<span class="HOEnZb"><font color="#888888"><br>
- Jeff<br>
</font></span></blockquote></div><br></div>