IronPython, IronRuby -- Compiler as a Service - Dynamic business objects etc..

IronPython, IronRuby -- Compiler as a Service - Dynamic business objects etc..

Old forum URL:

rfcdejong posted on Tuesday, June 29, 2010

We have the need for dynamic created silverlight content, but ofcourse working with CSLA business objects behind. Around a year ago i modified the CSLA business objects so that properties are dynamicly created and added. The need for dynamic BusinessRules, Dynamic everything, etc.. so many complex stuff is there. Customers want to implement there own rules and define there own views. But sadly our customers aren't developers and things will get complex real fast. Implimenting an custom inhouse engine won't be smart for sure.

Anyway. i'm getting away from my original discussion.

Are more people intrested in dynamic (compiler as a service) business objects / silverlight content / etc?
Or maybe better, is there someone with experience with IronPython or IronRuby?

PS: I think i'll go for IronPython.

bartol replied on Tuesday, June 29, 2010


I am using IronPython with a WPF application with great success. I use it both as an internal scripting engine for automating certain development tasks and as a "compiler as a service" in the Business Layer for dynamic rules and calculations. This is the second project where I do this and the only complications are marshalling very complex types back and forth. 

I chose IronPython instead of IronRuby because it is more mature and because IronRuby wasn't RTW at the time. It is 1.0 now so choose whichever you like most.


rfcdejong replied on Wednesday, June 30, 2010

There is alot of information about dynamic language runtime, there seems to be alot more need for. in C# 5.0 andrew showed DLR in C#, but i've the feeling that that'll take too long and i must 'play' with IronPython hehe.

Beside IronPython i saw Mono.CSharp, CSharpCodeProvider, etc.. as DLR languages.

rfcdejong replied on Tuesday, October 19, 2010

First: Sorry for bumping an 4 months old topic, but i just want to update on our status.

Bys the looks of it we aren't going to use IronPython nor IronRuby, but extending Csla objects with DLR code ourself.
The biggest reason is that IronPython didn't feel right to me and some others here.. and we like to stay more on the C# side.

Copyright (c) Marimer LLC