Orion Edwards wrote in post #1072378: > I'm not sure exactly why this happens, I think it's something to do with > how the .NET runtime itself delay-loads assemblies and the rules it has > for looking for dependent dll's
> There are three ways I know of to work around this: > 1. Use Dir.chdir to switch your working directory to > D:\Programs\Univeris\FooBoo\bin before you start loading the dll's > 2. Add to ruby's load path using $: << 'D:\Programs\Univeris\FooBoo\bin' > 3. Hook the CLR's AssemblyResolve event... this is a bit more complicated, > you can look up how this works on MSDN or I can tell you more if you'd > like > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core Thank you very much. Everything worked just fine. -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
