That's a bit ambiguous. If your C# library uses attributes I don't see why you wouldn't be able to reflect over those types with IronRuby and execute the attribute.
But using attributes in Ruby that is a totally different story. Luckily ruby has a different idea about classes and you can use class methods to reach a similar effect. For example ASP.NET MVC uses attributes to do its job, but IronRubyMvc has no need for them because it uses those class methods. http://github.com/casualjim/ironrubymvc/blob/master/IronRubyMvc/Controllers/controller.rb#L173 --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Blog: http://flanders.co.nz Twitter: http://twitter.com/casualjim Author of IronRuby in Action (http://manning.com/carrero) On Mon, Jan 11, 2010 at 3:31 PM, andrew Wilson <a.wilso...@gmail.com> wrote: > That worked! That would be a fun bug to track down. :) > > I was worried that it was reflection against an attribute, because the > documentation on the IR site seems to suggest that attributes still aren't > supported in .net API interop. ( > http://ironruby.net/Documentation/.NET/API_Guidelines) > > Thanks again! > -A > > > -- > When I wrote this, only God and I understood what I was doing. Now, God > only knows - Karl Weierstrass > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
