Editing IronPython (section)

== Interface extensibility ==
One of IronPython's key advantages is in its function as an extensibility layer to application frameworks written in a .NET language. It is relatively simple to integrate an IronPython interpreter into an existing .NET application framework. Once in place, downstream developers can use scripts written in IronPython that interact with .NET objects in the framework, thereby extending the functionality in the framework's interface, without having to change any of the framework's code base.<ref name=dot-net-example>{{cite web
 | url = http://www.resolversystems.com/documentation/index.php/Dot_Net_Objects_in_the_Grid
 | title = Using .NET objects from IronPython in Resolver One
 | access-date = 2008-11-18
 | archive-url = https://web.archive.org/web/20090114131717/http://www.resolversystems.com/documentation/index.php/Dot_Net_Objects_in_the_Grid
 | archive-date = 2009-01-14
 | url-status = dead
 }}</ref>

IronPython makes extensive use of [[Reflection (computer science)|reflection]]. When passed in a reference to a .NET object, it will automatically import the types and methods available to that object. This results in a highly intuitive experience when working with .NET objects from within an IronPython script.