I'm trying to add an assembly into Powershell but I keep getting:
Exception calling "LoadFrom" with "1" argument(s): "Could not load file or assembly "path etc" or one of its dependencies. Access is denied."
Does anyone know why I'm getting "Access Denied", I'm also running Powershell as admin and checked the .dll properties.
# Load the assembly. I used a relative path so I could off using the Resolve-Path cmdlet
$ScriptDirectory = (gi $PSCommandPath).DirectoryName
Join-Path $ScriptDirectory "taglib-sharp.dll"
[Reflection.Assembly]::LoadFrom( (Resolve-Path "$ScriptDirectory"))
This approach is also calling the Reflection library and the LoadFile static method.
Load a Custom DLL from PowerShell
One of the amazing features of PowerShell is its amazing reach. You can interact with the file system, the registry, certificate stores, COM, WMI, XML, cmdlets, providers … the list seems to go on forever.
One important extension point is the ability to seamlessly interact with .NET DLLs. These are most commonly shipped in SDKs, and many people have made use of this.