PowerShell Binary Module assembly dependency error

Question

I am developing PowerShell binary module. It uses Json.NET and other libraries.

I am getting this exception "Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.'

On hard drive I have an updated version of it (version 7.0.2)

Problems like that are easily solved in console, web or desktop application, with app.config or "web.config" via lines like this

<dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" culture="neutral" publicKeyToken="30ad4fe6b2a6aeed" />
    <bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" />
  </dependentAssembly>

How can I do something similar for PowerShell binary module?

score 7 · Answer 1 · answered Jun 21 '17 at 11:09

After coming across this issue myself while developing a PowerShell module that uses multiple 3rd party libraries (Google API, Dropbox, Graph, etc) I found the following solution was the simplest:

public static Assembly CurrentDomain_BindingRedirect(object sender, ResolveEventArgs args)
{
    var name = new AssemblyName(args.Name);
    switch (name.Name)
    {
        case "Microsoft.Graph.Core":
            return typeof(Microsoft.Graph.IBaseClient).Assembly;

        case "Newtonsoft.Json":
            return typeof(Newtonsoft.Json.JsonSerializer).Assembly;

        case "System.Net.Http.Primitives":
            return Assembly.LoadFrom("System.Net.Http.Primitives.dll");

        default:
            return null;
    }
}

Note in the method, I've got two possible ways to reference the assembly, but both of them do the same thing, they force the current version of that assembly to be used. (Regardless if it is loaded via class reference or dll file load)

To use this in any cmd-let add the following event handler in the BeginProcessing() method of the PSCmdLet.

AppDomain.CurrentDomain.AssemblyResolve += CurrentDomain_BindingRedirect;

Tested with module written in .NET Standard 2.0 and Powershell and Powershell Core — Pawel Wujczyk, May 21 '20 at 15:02
I ultimately did a variation on this, but discovered that best practice was to require users to invoke a cmdlet dedicated to wiring this. Otherwise, ensuring that `AppDomain.CurrentDomain.AssemblyResolve += CurrentDomain_BindingRedirect;` was always called before code that required special binding in all cases was ... [challenging](https://stackoverflow.com/questions/9099309/where-to-handle-assemblyresolve-event-in-a-class-library). — Eric Patrick, Jun 20 '20 at 02:21
Starting from PS 5.0 you can attach AssemblyResove event handler from inside a class implementing an IModuleAssemblyInitializer interface. Example: https://learn.microsoft.com/en-us/powershell/scripting/dev-cross-plat/resolving-dependency-conflicts?view=powershell-5.1#add-an-assemblyresolve-event-handler-to-create-a-dynamic-binding-redirect — Giorgi Chakhidze, Aug 06 '21 at 21:41

score 2 · Answer 2 · edited May 23 '17 at 10:29

2

The closest i've found so far is:

Add the problem assembly to the manifest's RequiredAssemblies - this causes it to be loaded into the AppDomain when the module is loaded.
Use the code from this SO answer - it adds an AssemblyResolve handler to the current AppDomain, which searches for assemblies already loaded and returns ones which match by strong name and PublicKeyToken
After using the module, you have to do the following to avoid stack overflows when exiting: [System.AppDomain]::CurrentDomain.remove_AssemblyResolve($OnAssemblyResolve)

Steps 1 and 2 could both be encapsulated in the module, but step 3 can't, which means this isn't suitable as a general solution - the caller has to know about it. So I'm still searching for a better way.

edited May 23 '17 at 10:29

Community

1
1

answered Mar 18 '17 at 22:11

ben

1,441
2
16
21

Thanks for answer, but I think this is not a good solution. Please let me know if you come up with better solution. I am still searching for solution. – TIKSN Mar 20 '17 at 08:01
I agree it's not a good solution. I think the stack overflow is caused by the call to `[System.AppDomain]::CurrentDomain.GetAssemblies()`. You might avoid this by hard-coding the specific assemblies you want to resolve in your event handler script (in step 2 above), and returning null for everything else. For now I've avoided the problem a different way - for me it was with System.Reactive which requires binding redirects in .NET4.6, but by downgrading to .NET4.5.2 the problem has gone away. – ben Mar 20 '17 at 11:30

score 0 · Answer 3 · edited May 23 '17 at 11:47

0

You need to add a manifest to your module.

The simplest way is:

New-ModuleManifest -RequiredAssemblies:"path\to\newtonSoft.dll"

Then modify the manifest file manually for any other tweaks.

If the manifest doesn't solve the problem, you may need to pull out the nuclear hammer and set the binding redirects for ALL of powershell as mentioned in Powershell - Assembly binding redirect NOT found in application configuration file

edited May 23 '17 at 11:47

Community

1
1

answered Sep 17 '15 at 16:40

Eris

7,378
1
30
45

I used required assembly, but it did not works. I am delivering my module through gallery, I can't require all user to tweak their powershell global config files, I won't do it even for my PC, locally. – TIKSN Sep 18 '15 at 20:30
The question relates to binding redirects. The RequiredAssemblies key in the manifest tells powershell which assemblies to load, but doesn't allow binding redirects. – ben Mar 18 '17 at 21:30

score 0 · Answer 4 · edited Jan 17 '17 at 03:08

For binary modules, there are a few keys that need to be populated in the manifest file for successful import/functionality:

RootModule = <'binaryModule.dll'>
RequiredAssemblies = <'binaryModule.dll'>
CmdletstoExport = '*' <--no need to restrict anything here, as
    only the public functions you've developed in the assembly
    will be exported to the user.

Those are the only keys you need to populate for the module to 'work' -- though I highly suggest combing through the .psd1 file generated byNew-ModuleManifest -path MyNewModule.psd1 to what other metadata values would help enrich the functionality of your module.

Also, ensure the names of the directory structure, .psd1 file, and assembly are all consistent.

SampleModule\
SampleModule\SamleModule.dll
SampleModule\SampleModule.psd1

...that should do it.

My question is not how to load types or assemblies, my question is hot to redirect assembly version. — TIKSN, Jan 18 '17 at 21:30

PowerShell Binary Module assembly dependency error

4 Answers4

Linked