Docusign.Esign.dll的继承问题继承了RestSharp依赖关系 [英] Dependency Issues with Docusign.Esign.dll's inherit RestSharp Dependency

问题描述

我正在使用Visual Studio中包含多个项目的解决方案。项目的一个区域需要RestSharp 106.10.1，在另一个项目（需要与之交谈）中，我们具有Docuign.ESign.dll，该文件具有RestSharp 106.3.1作为内部依赖项。尝试使用Docusing dll运行项目时，出现运行时错误

I am working with a solution in visual studio that has multiple projects in it. One area of the project requires RestSharp 106.10.1, and in another project (that it needs to talk to) we have the Docuign.ESign.dll that has RestSharp 106.3.1 as an interior dependency. When trying to run the project with the Docusing dll, we get a run time error of

无法加载文件或程序集'RestSharp，Version = 106.3.1.0，区域性= neutral，PublicKeyToken = 598062e77f915f75'。系统找不到指定的文件。

"Could not load file or assembly 'RestSharp, Version=106.3.1.0, Culture=neutral, PublicKeyToken=598062e77f915f75'. The system cannot find the file specified."

该dll似乎具有自己的其余版本Sharp，但与dll版本冲突。请放心，我们在解决方案的其他地方使用。我尝试下载docusign dll源代码，更新依赖项并创建新的dll，但这会破坏docusign代码，并且我尝试在项目中的app.config中执行绑定重定向，以便它使用其较低的版本，但我没有成功。我真的可以在这里使用一些帮助，我们将不胜感激。

The dll seemingly has its own version of rest sharp, but it conflicts with the version of rest sharp we are using elsewhere in the solution. I've tried downloading the docusign dll source code, updating the dependencies, and creating a new dll, but that breaks the docusign code, and I've tried doing a binding redirect in an app.config in the project so that it uses its lower version, but I've had no success with that. I could really use some help here, any help would be appreciated.

推荐答案

我大约在同一时间遇到了相同的问题您的帖子。我的情况要简单一些，但是希望对您有所帮助。

I ran into the same issue about the same time as your post. My situation is a little simpler, but I hope this helps.

是的，似乎DocuSign.eSign.dll确实想要使用RestSharp版本106.3.1。这可能是DocuSign DLL中的错误，所以我希望他们的开发人员中的一个正在监视docusignapi标签并可以解决这个问题。

Yes, it seems the DocuSign.eSign.dll really wants to use RestSharp version 106.3.1. This may be a bug in the DocuSign DLL, so I hope one of their developers is monitoring the docusignapi tag and can address this.

我的项目只是一个ASP.NET C＃WinForms Web应用程序，可让您填写一些信息，然后向DocuSign发送请求以发送用于签名的文档。我所有的以DocuSign为中心的代码都在单独的程序集中，因此我只应处理DocuSign.eSign.dll和RestSharp.dll的1个副本。

My project is just a ASP.NET C# WinForms web app which lets you fill in some info and then send a request to DocuSign to send out documents for signatures. All my DocuSign centric code is in a separate assembly, so I should only be dealing with 1 copy of DocuSign.eSign.dll and RestSharp.dll.

首次创建时在该项目中，我使用了最新版本的DocuSign.eSign（4.3.0）。它引入了RestSharp 106.3.1的依赖关系，我立即将其更新为106.10.1（可能是一个错误）。编译时，我收到有关找不到RestSharp 106.3.1的警告，并且在运行时，当找不到RestSharp 106.3.1时，应用程序崩溃。我今天大部分时间都在使用DocuSign代码示例来逐步更新各个部分（.NET版本，DocuSign.eSign，RestSharp），以尝试使其使用最新的软件包版本。

When I first created the project, I used the latest versions of DocuSign.eSign (4.3.0). It brought in the dependency of RestSharp 106.3.1, which I promptly updated to 106.10.1 (probably a mistake). Compiling I get a warning about not finding RestSharp 106.3.1 and at runtime, the app crashes when RestSharp 106.3.1 can't be found. I spent most of the day today working with a DocuSign code sample updating various parts (.NET version, DocuSign.eSign, RestSharp) step-by-step to try to get it to use the latest package versions.

这是有效的方法：
更新您的解决方案以使用最新版本的DocuSign和RestSharp。编译时，我希望您会看到版本冲突的警告。然后，对于显示此警告的每个项目，修改app.config文件，并将RestSharp的dependentAssembly部分更改为：

This is what works: Update your solution to use the latest versions of DocuSign and RestSharp. When you compile I expect you'll see the conflicting version warning. Then for every project that is showing this warning, modify the app.config file and change the dependentAssembly section for RestSharp to:

  <dependentAssembly>
    <assemblyIdentity name="RestSharp" publicKeyToken="598062e77f915f75" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-110.0.0.0" newVersion="106.0.0.0" />
  </dependentAssembly>

我对oldVersion使用了扩展范围，以确保DocuSign要使用的RestSharp版本被覆盖。 newVersion使用 106.0.0.0而不是 106.10.1，因为这是Visual Studio中报告的版本号。如果您在项目参考中选择RestSharp并查看其属性，则会看到106.0.0.0，而不是106.10.1。在构建日志中（选择诊断时），即使文件本身的属性为106.10.1，您也会看到它是融合名称。无论如何，这就是对我有用的。

I used an extended range for the oldVersion to make sure the RestSharp version DocuSign wants to use is covered. The newVersion uses "106.0.0.0" instead of "106.10.1" because that's the version number being reported in Visual Studio. If you select RestSharp in the project references and look at its properties, you'll see 106.0.0.0, not 106.10.1. In the build log (when Diagnostics is selected), you'll see this is it's "Fusion name" even though the properties of the file itself will say 106.10.1. Anyway, that's what is working for me.

如果我可以回答任何问题或提供其他信息，请告诉我。

If I can answer any questions or provide additional information, please let me know.

谢谢，
兰迪

这篇关于Docusign.Esign.dll的继承问题继承了RestSharp依赖关系的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！