# IronRuby support for .Net 5.0

**URL:** <https://www.ruby-forum.com/t/ironruby-support-for-net-5-0/204010>\
**Category:** IronRuby\
**Created:** [March 3, 2011, 10:21am UTC](https://www.ruby-forum.com/t/ironruby-support-for-net-5-0/204010 "2011-03-03T10:21:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [March 3, 2011, 10:21am UTC](https://www.ruby-forum.com/t/ironruby-support-for-net-5-0/204010/1 "2011-03-03T10:21:32Z")

</div>

What is the roadmap for .Net 5.0 support in IronRuby?

Piotr Nestorow

---

<div class="post-metadata">

**Author:** ![Piotr\_Nestorow](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/898d66/32.png) [@Piotr\_Nestorow](https://www.ruby-forum.com/u/Piotr_Nestorow)\
**Post date:** [March 3, 2011, 11:47am UTC](https://www.ruby-forum.com/t/ironruby-support-for-net-5-0/204010/2 "2011-03-03T11:47:03Z")

</div>

Is it already out? Are there any previews of it? Showcases? Anything?

On Thu, Mar 3, 2011 at 9:48 AM, Piotr Nestorow \<

---

<div class="post-metadata">

**Author:** ![Piotr\_Nestorow](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/898d66/32.png) [@Piotr\_Nestorow](https://www.ruby-forum.com/u/Piotr_Nestorow)\
**Post date:** [March 3, 2011, 5:39pm UTC](https://www.ruby-forum.com/t/ironruby-support-for-net-5-0/204010/3 "2011-03-03T17:39:40Z")

</div>

There is no formal roadmap. Basically once .NET 5 is released in any  
form we’ll assess what (if anything) needs to be done. We won’t get  
our hands on it before it’s released, so this will be unlike previous  
releases where IronRuby released a compatible version with a .NET  
pre-release, like we did with .NET 4 releases … unless Tomas  
front-loads this work =P.

This is quite like how Mono doesn’t know what they need to do to be  
.NET 5 compatible…

To speculate, presumably nothing will _need_ to be done, but there  
might be some potential for iterating on the .NET integration  
features. Or if the hosting APIs make it into the framework  
(Microsoft.Scripting.dll), we can take a dependency on those. But we  
won’t know for sure until it’s releases.

~Jimmy

On Thu, Mar 3, 2011 at 5:29 AM, Andrius Bentkus