braintree / braintree_dotnet

Braintree .NET library
https://developer.paypal.com/braintree/docs/start/overview
MIT License
136 stars 73 forks source link

Can't find System.Xml.XPath.XmlDocument.dll #99

Closed Fams1973 closed 4 years ago

Fams1973 commented 4 years ago

General information

Issue description

Can't find System.Xml.XPath.XmlDocument.dll 4.0.2.0 It does not seem to be up on NuGet. This is causing issues when running a refund transaction in an Azure Function. For some reason the NuGet packages states that anything higher than 4.3 should work for this package but does not seem to. The reference is missing completely. There may be a binding redirect I can do somehow but stuck at the moment.

image

image

Error Message: "Could not load file or assembly 'System.Xml.XPath.XmlDocument, Version=4.0.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.":"System.Xml.XPath.XmlDocument, Version=4.0.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"} | System.Exception {System.IO.FileNotFoundException}

Stack Trace: at Braintree.NodeWrapper.GetNode(String path) at Braintree.NodeWrapper.IsSuccess() at Braintree.ResultImpl1..ctor(NodeWrapper node, IBraintreeGateway gateway) at Braintree.TransactionGateway.<RefundAsync>d__18.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()

Fams1973 commented 4 years ago

Correction: Looks like 4.0.2.0 is actually System.Xml.XPath.XmlDocument 4.3.0. For some reason this assembly is not being published along with the braintree assembly and causing issues. Any suggestions would be appreciated.

Fams1973 commented 4 years ago

Looks like this may be a problem with Azure Functions not pulling across all the assemblies. I will close. thank you

crookedneighbor commented 4 years ago

Thanks for the followup.