Microsoft's .NET Framework arrived with two languages, C# and Visual Basic. Then came the Iron Languages, .NET compatible implementations of Ruby and Python which Microsoft "let go of" in 2010. Nowadays Microsoft is again embracing Python. Here's an account of Python's still evolving relationship with .NET
This trip down memory lane was triggered by the recent news of the release of a new version of Python.NET which begged the question of what had become of Iron Python, one of Microsoft's dynamic Iron-languages on the .NET platform.
First of all let's clear up the confusion arising out of having two versions of Python for .NET: Python.NET and IronPython.
While not as well known as IronPython, Python.NET predates it but had seen no updates in recent years and was still on the Python 2.x branch. Recently it emerged from apparent hibernation with the release of Python.NET 3.0.0, revitalizing what many assumed to be a dead project.