tags:

views:

433

answers:

1
+2  Q: 

Internals visible to Boo (Binsor)

I am using Castle Windsor for IoC and I want to use Binsor to define my configuration. I want to let my internals be visible to Boo. I have tried to mark my assembly with InternalsVisibleTo("Boo.Lang") but that didn't do the job. I have tried InternalsVisibleTo("Rhino.Commons") because I have noticed that the exception is thrown from within Rhino.Commons.Binsor.BooComponentInstaller but that doesn't work neither. Any ideas?

+1  A: 

InternalsInvisible isn't available yet in Boo, tried using it in 2007/early 2008 for testing purposes.

There is an issue logged against this in Boo's codehaus page : Boo Issue around this

Seems like it is scheduled to be fixed in V0.9.3

saret  2009-10-20 08:29:30

related questions

Subsonic Vs NHibernate
How to check For File Lock in C# ?
Is nAnt still supported and suitable for .net 3.5/VS2008?
Limit size of Queue<T> in .NET?
Viewstate invalid when using Safari
Free OCR library
Unhandled Exception Handler in .NET 1.1
Localising date format descriptors
Get a new object instance from a Type in C#
VFP .NET OLEdb provider does not work in Win 64-Bits. Help
.NET Testing Framework Advice
Embedded Database for .net that can run off a network
Automatically update version number
Homegrown consumption of web services
How do you migrate a large app from VB6 to VB .net ?
.NET Migrations Engine
Adding Scripting functionality to .NET applications
SQLite and XSD
Floating Point Number parsing: Is there a Catch All algorithm?
How do I programmatically create a PDF in my .NET application?
How do I sync the SVN revision number with my ASP.NET web site?
XSD DataSets and ignoring foreign keys
Anatomy of a "Memory Leak"
Reliable Timer in a Console Application
How do I calculate relative time?