chucknorris/dropkick — Issue #35: Bug: Loading deployment spec from a remote location causes error
Author: Kaithos
Created: 2012-02-02 16:10:37+00:00
State: open

Under the .NET 4.0 framework, dropkick can not load a deployment specification assembly from a remote location. The error message thrown by the CLR is as follows.

System.NotSupportedException: An 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 this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence)
at System.Reflection.Assembly.LoadFile(String path)
at dropkick.Engine.DeploymentFinders.AssemblyWasSpecifiedAssumingOnlyOneDeploymentClass.Find(String assemblyName) in c:\Solutions\dk-fc\product\dropkick\Engine\DeploymentFinders\AssemblyWasSpecifiedAssumingOnlyOneDeploymentClass.cs:line 45
at dropkick.Engine.DeploymentFinders.MultipleFinder.Find(String deployment) in c:\Solutions\dk-fc\product\dropkick\Engine\DeploymentFinders\MultipleFinder.cs:line 25
at dropkick.Engine.Runner.Deploy(String commandLine) in c:\Solutions\dk-fc\product\dropkick\Engine\Runner.cs:line 66