-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[API] Issue when attempting to execute run command through API #769
Comments
That looks bad - definitely an issue. Looks like something was not set up properly for the container. |
I'll look into this soon myself too. This is def very blocking issue |
I'm looking into this, and I honestly am at a loss. Why doesn't Choco.exe error, but chocolatey.lib does? Hmmm. |
Ohhhhhh. It looks like the issue is we're both using Reactive, but you're using a much older, and different version. Edit: Monkey patched this by adding this code in ChocolateyGUI:
|
That's a start...I wonder if I should do that for all things where the public key token is Chocolatey's and load them. |
When using the API, it should resolve merged assemblies but it may not if there is an assembly handler registered. Before loading up code that resolves external assemblies, register an AssemblyResolve handler with the purpose of determining if the assembly has Chocolatey's Public Key token or not. If it does, use Chocolatey's merged assembly instead of the conflicting assembly.
@RichiCoder1 can you take a look at #776? |
I think #776 may be the answer here, but it will need validated on the next beta release (to show that it is not too late by then to register the handler). |
…ly-handler (GH-769) API - Resolve Merged Assemblies
* stable: (maint) use case insensitive compare for token (GH-769) API - Resolve Merged Assemblies
What You Are Seeing?
An exception when running any sort of
run()
command.What is Expected?
Executing a
run
command should work fine.How Did You Get This To Happen? (Steps to Reproduce)
With the latest chocolatey.lib
0.9.10-beta-20160531
trying and run:Output Log
The text was updated successfully, but these errors were encountered: