Your app is not the thing trying to load that assembly, IronRuby is. So,
you'll need to add that to IronRuby's app.config.

That said, why are you trying to load an assembly from a network location in
your tests? That is, IMO bad testing practice.

--
Will Green
http://hotgazpacho.org/


On Mon, Jun 21, 2010 at 11:39 AM, Mohammad Azam <azamsh...@gmail.com> wrote:

> I am using .NET 4.0 with IronRuby to invoke some methods on WatiN framework
> 2.0.10.928.
>
> I keep getting the following error when loading the WatiN assemblies:
>
>
> C:\Projects\IronRubyDemo\IronRubyDemoSolution\BusinessObjects>ir -S spec
> testacc
> ountbalanceUI.rb
> C:/IronRuby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:30:in
> `require': A
> n attempt was made to load an assembly from a network location which would
> have
> caused the assembly to be sandboxed in previous versions of the .NET
> Framework.
> This release of the .NET Framework does not enable CAS policy by default,
> so thi
> s load may be dangerous. If this load is not intended to sandbox the
> assembly, p
> lease enable the loadFromRemoteSources switch. See
> http://go.microsoft.com/fwlin
> k/?LinkId=155569 for more information. (LoadError)
>         from
> C:/IronRuby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:30:in
>  `require'
>
>
> So, I went to the App.config file of my project and added the following
> lines:
>
> <?xml version="1.0" encoding="utf-8" ?>
> <configuration>
>
>   <runtime>
>     <loadFromRemoteSources enabled="true" />
>   </runtime>
>
> </configuration>
>
> I tried running it again and encountered the same problem. Any ideas!
> --
> Mohammad Azam
> MVP (Microsoft Valuable Professional)
> www.highoncoding.com
> www.azamsharp.com
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core@rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
>
_______________________________________________
Ironruby-core mailing list
Ironruby-core@rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core

Reply via email to