Commented Issue: Update-Database fails when working from a mapped network drive [856]

Updating worked from a local drive, stopped working after moving to a network drive and started working again after moving back to a local drive.
Directories are binary identical (except for obj and bin directories).

Windows 7 x64, Visual Studio 2010.

```
PM> Update-Database -Verbose -Force
Using StartUp project 'MyFirstProject'.
Using NuGet project 'MySecondProject'.
Exception calling "LoadFrom" with "1" argument(s): "Could not load file or assembly 'file:///L:\MySolution\packages\EntityFramework.5.0.0\tools\EntityFramework.PowerShell.Utility.dll
' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)"
At L:\MySolution\packages\EntityFramework.5.0.0\tools\EntityFramework.psm1:398 char:62
+ $utilityAssembly = [System.Reflection.Assembly]::LoadFrom <<<< ((Join-Path $toolsPath EntityFramework.PowerShell.Utility.dll))
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException

You cannot call a method on a null-valued expression.
At L:\MySolution\packages\EntityFramework.5.0.0\tools\EntityFramework.psm1:399 char:50
+ $dispatcher = $utilityAssembly.CreateInstance <<<< (
+ CategoryInfo : InvalidOperation: (CreateInstance:String) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull

Exception calling "CreateInstanceFrom" with "8" argument(s): "Could not load file or assembly 'file:///L:\MySolution\packages\EntityFramework.5.0.0\tools\EntityFramework.PowerShell.d
ll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)"
At L:\MySolution\packages\EntityFramework.5.0.0\tools\EntityFramework.psm1:431 char:31
+ $domain.CreateInstanceFrom <<<< (
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
```
Comments: **EF Team Triage:** The migrations commands require full trust to run. Because you are running from a network share it looks like you are running in a lower trust level. In the past we have made the decision that the migrations commands would require full trust because it reduces the complexity of the implementation.