Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Pumping Iron: Dynamic Languages on .NET

1 hour, 21 minutes, 57 seconds


Right click “Save as…”

As is commonly known, Microsoft is developing IronPython and IronRuby, .NET implementations of the popular open-source programming languages Python and Ruby.

While it is clear that Microsoft wants to attract existing Python and Ruby developers to .NET, the role of IronPython and IronRuby for existing .NET developers is less clear. What value is there for a .NET developer in learning IronPython? What are the tradeoffs between IronRuby and a more traditional .NET language like C# or VB? Harry Pierson, new PM for IronPython, will discuss where dynamic . languages fit in the.NET developers toolbox.

To learn more about IronPython visit the IronPython project page on Codeplex or Harry’s blog, he is writing quite a bit on that IronPython topic Wink

Get the slides


Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • Greg Braygbrayut Check out PhraseMeme Scanner for Windows Phone at ​PhraseMeme.​com

    Excellent presentation! It is very exciting to see the push for dynamic languages being included in the .NET ecosystem.  I really wish that Visual Studio had full support for IronPython. The IronPython Studio project was nice, but it did run on V1.1 so it was quite out dated. I am optimistic about the new IronPython Studio example being included in the Visual Studio 2010 SDK, but it would be a shame if a 3rd party ended up beating Microsoft at creating the best IronPython IDE  Tongue Out


    Keep up the great work!

  • BassBass Knows the way the wind is flowing.

    The slides link doesn't seem to work.

  • Allan LindqvistaL_ Kinect ftw

    i totally agree Smiley i'd love to get out of netbeans for our RoR app, and ive figured we sould use iron ruby instead. but the tool chain is at the very best, inobvious Sad


    what i want to be able to do is go, File > new project > ironpython/ruby Smiley

    it seems like you put in so much hard work that will go unnoticed by many because its not visible from vs.. and what about debugging and such?


    perhaps this will change in vs2010 because its more easily extensible, but better vs support is really needed Smiley



    someone asks about vs integration at the end of the video, an sdk sample is.. well.. ok.. but its a far cry from whats needed Smiley we need full support like ther is for c# anc vb and f#.. if vs is as extensible as they say, this should not be a huge project Smiley

    without vs support iron python/ruby is little more than an academic toy in my book Sad

  • http://cid-c3d6cc95a9707c05.skydrive.live.com/browse.aspx/Public/IronPython^_DK^_Tour

    Then click the Pumping Iron (MDCC) document to get to the page with the Download link. SkyDrive URL's suck for sharing.

  • Point taken! the skydrive url’s are probably not the best for sharing.

    If it’s still not working you can grab the slides from this url instead: http://diku.dk/begivenheder/DIKUtalks/diku_talk_1/Pumping_Iron.pdf/

  • I totally agree! We don’t have a great tooling story to tell in Visual Studio!
    But fortunately you can change and influence on that, by giving your vote too exactly that feature request on Microsoft Connect!

    Want to see IronPython support in a future version of Visual Studio?

    (Link taken from ironpython.codeplex.com)

  • It is not that it sucks. You could have used the HTML Source editor and pasted the HTML embed code from the skydrive page. But apparently it does not work on Channel 9. It does work with blogs though.

Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.