> The call to assign the results of Parse to P always fails unless I
>
> a) Do what Ivan suggested and copy to the bin folder
> b.) Modify ir.exe.config to include the path to the actual .dll
I would suggest neither of these =P See below.
> I was reading the source code this evening and noticed
Jimmy,
So I decided to debug this out a bit for myself. Before I go too far, here
is how my require headers are setup:
require 'System.Xml.Linq, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089'
require 'System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral,
PublicKeyT
f andrew Wilson
Sent: Tuesday, January 12, 2010 8:43 AM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] InternalsVisibleTo
Jimmy,
Yes that worked, but it did point out another problem. When I do:
My::Domain.constants
I have somewhere like 15 references to .dll's that won't l
hementi)
>
>
> --
>
> Message: 1
> Date: Mon, 11 Jan 2010 22:06:23 -0700
> From: andrew Wilson
> To: ironruby-core@rubyforge.org
> Subject: [Ironruby-core] InternalsVisibleTo
> Message-ID:
>
I know this is a bit of a longshot, but has anyone got an internalsvisibleto
attribute to work so they could debug internal classes from ir itself? I
tried to add the namespace "ir" and public key to the assembly I was trying
to test to no avail.
Im building out some rspec & IronRuby tests of my
