From: "John R. Pierce" <john@...>
Date: 2003-09-27T12:49:20+09:00
Subject: Re: RubyDotNet r4 and namespaces

On Sat, 27 Sep 2003 10:44:00 +0900, James Britt wrote:

> I grabbed the r4 release of RubyDotNet from 
> http://www.saltypickle.com/rubydotnet, and it works great (well, on my 
> laptop.  My main PC seems to have issues with multiple versions of the 
> .net framework installed).

Very interesting....both of us (the developers) are running our machines with
both version of .NET (1.0 and 1.1) as we develop this product. Can you provide
us specific errors you are getting?

> I had no trouble writing my own C# class and calling it from Ruby 
> (pretty sweet).  But I if put my class in a namespace I can't get the 
> Ruby code to find it. I get errors about an unknown constant (i.e., the 
>   namespace for the C# class).

Are you building your custom C# class under .NET 1.1? Are you referencing the
dll using a fully qualified path including extension?  If so to both of these,
can you provide a copy of your class either on this mailing list or directly to
me (if it is too big).  I'd like to see this.

We actually have this exact scenario in a test case included in the
distribution.  If you look in the Ruby\tests folder you will find a test file
called "TestCoreBridge.rb".  Inside this file there are several test cases with
respect to the class "TestClasses.NumberHolder".  I'd be curious if this test
passes on your machine. To run the tests you must be in a command prompt that
has csc.exe in the path as the test will compile a custom c# class and then
access it.
 
> On a side note, is there a connection between RubyDotNet at 
> saltypickle.com, and the rubydotnet at rubydotnet.sourceforge.net, other 
> the (confusing) use of essentially the same name?

Gosh, what were we thinking? Guess we need a namespace to resolve conflicts. 
Anyways, www.saltypickle.com is the home the Ruby/.NET bridge.  We also run a
site on rubyforge.org called rubydotnet.  SourceForge already had a rubydotnet
project -- and we didn't know it until too late. Guess this explanation is still
confusing -- oh well.

Regards,

John