Oh, okay, that make sense, then. On Fri, Jul 31, 2009 at 4:02 PM, Mick Delaney <[email protected]> wrote:
> > basically when i compile my site it references rhino commons, which > references the boo.* assemblies, which are copied into my bin > directory. asp.net complains until i remove them. > i initialized the container myself in my UnitOfWorkApplication, > bypassing bindsor/boo so that's fine now. > I have some more errors but they're just because come dll's arent > marked as allow paritally trusted callers. am recompiling. > thanks for the quick reply > > On Jul 31, 3:06 am, Ayende Rahien <[email protected]> wrote: > > If you aren't using Binsor, you shouldn't have problems with that.Where > are > > you getting that? > > > > On Fri, Jul 31, 2009 at 2:35 AM, Mick Delaney <[email protected]> > wrote: > > > > > Hi, > > > > > I've built a site using Rhino Commons and am testing it under medium > > > trust, but I'm getting problem where Boo.Lang.Compiler is not > > > allowed. > > > > > has anyone come across this before? > > > > > i'm not actually using bindsor or boo so i guess i could fork the > > > codebase and remove all of it but i'd rather not. > > > > > is there another way to get around this? > > > > > cheers. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
