Found the issue here...

The machine where we copied the dlls from marked the .dll as blocked.

By right-clicking on the .dll you see "This file came from another
computer and might be blocked to help protect this computer"

By clicking "Unblock" it works fine.

Not a LinFu or NHibernate issue. Simply a CAS issue on my side as we
were copying dlls from one machine to another over RDP.

On Oct 13, 3:14 pm, Luka <[email protected]> wrote:
> I don't know what this exception means, but I am working on a x64
> windows and it works fine. If you think this is because of x64 try to
> just set target platform in project properties => build to x86.
>
> On Oct 13, 4:11 pm, bstack <[email protected]> wrote:
>
>
>
> > All,
>
> > I have an application using NServiceBus, Castle and NHibernate.
> > I am using LinFu as the NHibernate proxy factory with the following
> > configuration:
>
> > <property
> > name="proxyfactory.factory_class">NHibernate.ByteCode.LinFu.ProxyFactoryFac­tory,
> > NHibernate.ByteCode.LinFu</property>
>
> > Everything works fine on x86 machine. When I execture my application
> > on x64 machine, I get a failure with the following error:
>
> > Unhandled Exception:
> > Castle.MicroKernel.ComponentActivator.ComponentActivatorException:
> > ComponentActivator: could not instantiate
> > CCS.iPS.DPC.PublicService.Service.Component --->
> > System.Reflection.TargetInvocationException: Exception has been thrown
> > by the target of an invocation. ---> System.IO.FileLoadException:
> > Could not load file or assembly 'file:///D:\SVN\ccs\misc\experiments
> > \DPC\CCS.iPS.ServiceHost\bin\Debug\LinFu.DynamicProxy.dll' or one of
> > its dependencies. Operationis not supported. (Exception from HRESULT:
> > 0x80131515) ---> System.NotSupportedException: An attempt was made to
> > load a
> > n 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 this load may be dangerous. If this load is not intended
> > to sandbox the assembly, please enable the loadFromRemoteSources
> > switch. Seehttp://go.microsoft.com/fwlink/?LinkId=155569formore
> > information.
>
> > Does anyone know the problem?
>
> > Regards,
> > Billy- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" 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/nhusers?hl=en.

Reply via email to