# Using Ruby types in .NET: anything to watch out for?

**URL:** <https://www.ruby-forum.com/t/using-ruby-types-in-net-anything-to-watch-out-for/194476>\
**Category:** IronRuby\
**Created:** [September 6, 2010, 4:39pm UTC](https://www.ruby-forum.com/t/using-ruby-types-in-net-anything-to-watch-out-for/194476 "2010-09-06T16:39:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Davy\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/7ba0ec/32.png) [@Davy\_B](https://www.ruby-forum.com/u/Davy_B)\
**Post date:** [September 6, 2010, 4:39pm UTC](https://www.ruby-forum.com/t/using-ruby-types-in-net-anything-to-watch-out-for/194476/1 "2010-09-06T16:39:39Z")

</div>

Hi all,

first of all: thanks for this great project and the effort you’ve put  
into  
it, it’s very much appreciated 🙂

I plan on making extensive use of ruby object instances in my .NET code.  
With that i mean that we have a certain object model written in Ruby,  
and  
we’d like to use that in our .NET code. We’re going to use those  
instances  
quite a lot, so i just wanted to check if there are any known pitfalls  
to  
watch out for when doing this. The reason i’m asking is because most of  
the  
docs and the examples i’ve seen focus on the opposite approach: using  
.NET  
instances in Ruby.

I’ve done some preliminary experiments and my ruby instances work just  
fine  
when i call them from .NET… but i’m hoping to get some feedback here  
from  
people who have more extensive experience with this.

brs,  
Davy