Scott Hanselman

browse by category or date

IronPython and the DLR march on

March 22, '08 Comments [12] Posted in ASP.NET | ASP.NET MVC | DLR | Python | Ruby | Silverlight
Sponsored By

I've got a number of emails complaining that folks haven't heard much from the DLR (Dynamic Language Runtime) and things like IronPython and IronRuby.

I think it's due to mostly one thing, the fact that the ASP.NET Futures Page still says July 2007. That's one of the reasons I personally fought to have the ASP.NET MVC not use a Date in its name. It just makes things look, ahem, dated.

I'm working to get that page updated, but I just wanted to make sure folks know that there's lots going on around the DLR. I talked to Mahesh on a video call just yesterday.

There's lots going on and here's some collected resources for you:

Once you've had fun with all that, you might look at John's Dynamic Silverlight in ASP.NET MVC article.

Here's John and Jimmy's talk on Dynamic Silverlight at Mix08:

All other goodness is at http://dynamicsilverlight.net/. Enjoy.

« The Weekly Source Code 21 - ASP.NET MVC ... | Blog Home | 7 Blogging Statistics Rules - There is L... »

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. I am a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by ORCS Web
Comments [12]
Saturday, March 22, 2008 2:47:36 AM UTC
Also worth checking out Martin Maly's blog on DLR as a whole, some really good examples on writing your own dynamic language with the DLR. http://blogs.msdn.com/mmaly
Chris Hardy
Saturday, March 22, 2008 4:12:15 AM UTC
Thanks for the great start on DLR topic.

I hope this should move fast now. I would appreciate, if you spare some time and show us an example of LINQ working with IronRuby / IronPython.

LINQ with Dynamic languages would be a very interesting topic.

Thanks
Parag Kantharia
Saturday, March 22, 2008 7:55:41 AM UTC
I will continue to look for more information on such topics as IronPython, LINQ, Dynamic Language Runtime and IronRuby in coming days and weeks.

Josh Coswell
http://riverasp.net
Josh Coswell
Saturday, March 22, 2008 10:20:28 AM UTC
Thanks Scott. This is really useful. It's the kind of thing we couldn't get anywhere else.

Richard
Richard Bushnell
Saturday, March 22, 2008 11:31:43 AM UTC
It would be nice to see few short examples ( for a start ) like below

(1) Asp>net MVC with IronRuby
(2) LINQ with IronRuby
(3) Asp.Net with IronRuby

It would be nice to start some tutorials based on the topics above.

Why dig for a well, when fire appears suddenly.

Just my 2 cents

IronRuby
IronRuby
Saturday, March 22, 2008 5:11:05 PM UTC
About that whole 'Futures' thing, is there a blog by the people that are doing ASP.NET Ajax, because I'm kind of wondering what (if anything) is going on there? From the outside, it seems there is nothing happening. Not all teams are great at blogging like you (or the others on the ASP.NET MVC team).
Mike
Saturday, March 22, 2008 7:16:27 PM UTC
If you're interested in IronPython and Silverlight, I've done a series of tutorial articles with online and downloadable examples (including a web-ide for experimentation):

http://www.voidspace.org.uk/ironpython/silverlight/index.shtml

Michael Foord
Michael Foord
Saturday, March 22, 2008 9:11:03 PM UTC
DLR rocks!!!!
Marlon Grech
Sunday, March 23, 2008 5:00:09 AM UTC
Scott was kind enough to refer me to Bertrand Le Roy on the ASP.NET team for questions I had about the querySelectorAll support coming in ASP.NET AJAX. I'm looking forward to updates on ASP.NET Futures!

I'm excited about the prospects of developing ASP.NET code-behind (code-beside?) using the DLR!

As far as seeing LINQ work in the DLR, it would be nicer to see the idiomatic functional programming constructs native to both languages used for such functionality. Both languages already have lambda functions, map/filter/reduce, etc. It's redundant to use LINQ to Objects for such things.

Personally, I would like to see Merb on IronRuby (which would be easier and maybe even better than Rails) and TurboGears on IronPython.
Joe Chung
Monday, March 24, 2008 9:56:24 AM UTC
@ Joe Chung

Hi Joe, I have some interesting news to share with you.

Read here...
http://www.ruby-forum.com/topic/145427#new

As per John Lam ( PM IronRuby Team and DLR ) his priority goal remains to run Real Ruby Programs on IronRuby. And Real Ruby Programs are.... Rails, Merb, Active Record, DataMapper Etc..

As per this thread....
http://www.ruby-forum.com/topic/145965#new

It would be more interesting to know that you can even create Rails Program in any Ruby on Rails IDE and Paste the same codes in VS2008 and Run it easily with DLR without any Problems.

Just keep contributing there, if you would like to know more.

Cheers!
IronRuby
Tuesday, March 25, 2008 1:40:02 AM UTC
For me personally, most of the disappointment with asp.net futures is not the release date per se - but the poor options it leaves me for developing web apps with ironpython... Initially, I was so excited to be able to use ironpython with ASP.NET, but that excitement faded quickly when I realized the futures team had made it impossible to create custom controls in ironpython since everything inherited from their wicked scripting base classes... I think this is a shame as it greatly diminishes the usefulness of ironpython and asp.net! At this point, the talk about Jim Huginins mod to make django work with ironpython is probably the last hope that I have for ironpython, otherwise I might as well wait a few years until it matures.
Christian Toivola
Tuesday, April 01, 2008 10:46:17 PM UTC
Hi Scott,

DLR is something which looks really interesting. I've done a getting started post on my blog

http://blog.benhall.me.uk/2008/03/getting-started-with-ironpython.html

Definitely something I will be looking at in more detail.

Cheers

Ben
Ben Hall
Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.