[IronPython] Problem with Creating Executable using SharpDevelop

[Michael Foord]

Are there issues around assembly versions and the GAC? I'm thinking 
particularly of where newer versions of IronPython are released as 
drop-in replacements so the version numbers are not updated. If a 
previous version is in the GAC isn't there a likelihood that an 
application that ships with a newer version will still load the GAC'd 
older version... ?

My *impression* was that adding stuff to the GAC was a recipe for DLL 
hell and therefore it was better left to individual users rather than 
being automatic on installation. This opinion may be ill-informed however...

Michael

Dino Viehland wrote:
>
> The big problem w/ installing into the GAC from our perspective is 
> that assemblies in the GAC are fully trusted and can be loaded by 
> anyone. Combine this w/ the AllowPartiallyTrustedCallers attribute 
> which we apply to our assemblies and you potentially have a recipe for 
> disaster. In theory we believe this is ok because we’re also 
> SecurityTransparent but we haven’t had the deeper conversion w/ the 
> CLR team about combining all 3 of these so we continue to be 
> conservative and not install into the GAC.
>
> We should probably look into removing APTCA though – the reason why we 
> applied it in the 1.x time frame was due to a performance problem w/ 
> signed non-APTCA assemblies which may now be fixed in the CLR.
>
> As for actually doing the installation you now need to invoke gacutil 
> 5 times – once for each DLL. IronPython, IronPython.Modules, 
> Microsoft.Scripting, Microsoft.Scripting.Core, and 
> Microsoft.Scripting.ExtensionAttribute. In 2.6 there’ll be one more 
> assembly to add to the list – Microsoft.Scripting.Debugging.
>
> *From:* users-bounces at lists.ironpython.com 
> [mailto:users-bounces at lists.ironpython.com] *On Behalf Of *Jonathan March
> *Sent:* Friday, July 10, 2009 9:28 AM
> *To:* Discussion of IronPython
> *Subject:* Re: [IronPython] Problem with Creating Executable using 
> SharpDevelop
>
> Installing IP into the GAC is something apparently not much discussed 
> in polite company (e.g. AFAICT not at all in "IP in Action" or "IP URLs".)
>
> For us .net ignorami:
> * What is the downside to installing IP into the GAC? Is it that 
> different apps will be dependent on different IP versions so better 
> just to keep the IP DLLs together with each app?
> * Is installing into GAC still done by invoking gacutil twice as 
> described here:?
> http://www.manifold.net/doc/scripts.htm
>
> Thanks.
>
> On Fri, Jul 10, 2009 at 11:03 AM, Dino Viehland <dinov at microsoft.com 
> <mailto:dinov at microsoft.com>> wrote:
>
> In general you need IronPython to be present to run IronPython apps - even
> if they're compiled. And IronPython will need to be next to the app
> unless IronPython has been installed into the GAC (which we do not
> do by default). Also you probably want to include IronPython.Modules.dll
> as well in addition to the DLLs you have here. I imagine at some point
> in the future we could add some sort of tree shaking compiler support
> that links in IronPython w/ the app but we're a ways off from making
> that a priority.
>
> The SharpDevelop specific question I'm less sure about.
>
>
> > -----Original Message-----
> > From: users-bounces at lists.ironpython.com 
> <mailto:users-bounces at lists.ironpython.com> [mailto:users- <mailto:users->
> > bounces at lists.ironpython.com <mailto:bounces at lists.ironpython.com>] 
> On Behalf Of Kelie
> > Sent: Thursday, July 09, 2009 11:34 PM
> > To: users at lists.ironpython.com <mailto:users at lists.ironpython.com>
> > Subject: [IronPython] Problem with Creating Executable using
> > SharpDevelop
> >
> > Hello,
> >
> > I created a simple program with a few buttons, checkboxes, textboxes,
> > etc. and it worked fine. The form was created in the latest
> > SharpDevelop beta version (Version : 3.1.0.4077). Then I compiled the
> > solution. In the release folder there were these files:
> >
> > IronPython.dll
> > ManningsSolver.dll
> > ManningsSolver.exe
> > Microsoft.Scripting.Core.dll
> > Microsoft.Scripting.dll
> > Microsoft.Scripting.ExtensionAttribute.dll
> >
> > When tried on two computers with IronPython installed and with the
> > source code files, the program worked. But it failed on another
> > computer that does not have these. And error message was very
> > generic .NET error. I don't exactly remember what it was. Is this
> > normal?
> >
> > Btw, since I have SharpDevelop installed, do I have to install
> > IronPython in order to write programs in IronPython? Or does it matter
> > which version of IronPython I install. The answer seems to be "No"
> > because I see those .dll files for IronPython in this folder "C:
> > \Program Files\SharpDevelop\3.0\AddIns\AddIns\BackendBindings
> > \PythonBinding" which are dated Feb 2009. Guess they're not the
> > latest.
> >
> > Thanks,
> >
> > Kelie
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.ironpython.com <mailto:Users at lists.ironpython.com>
> > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com <mailto:Users at lists.ironpython.com>
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>   


-- 
http://www.ironpythoninaction.com/