我如何解决Nuget DLL地狱-无论我做什么VS坚持认为dll版本与软件包中的版本不同

在更新Nuget之后，我已经为DLL的地狱而奋斗了一个多星期。我设法通过手动编辑解决方案，项目和包文件解决了大多数问题。但是，无论我做什么VS都坚持认为dll版本与Nuget安装的版本不同。有问题的库是MailKit，在更新之前可以正常使用。现在，已安装的版本是2.4.1，但是尽管显示了正确的位置，属性网格仍坚持认为版本2.4.0是：

我尝试了以下所有方法，但都没有成功：

• 更新包-重新安装
• 手动删除Nuget缓存
• 手动删除计算机上2.4.0 dll的每个单个副本
• 在整个代码库中搜索对2.4.0的任何引用，然后手动编辑代码以删除引用或重新编号为正确的版本
• 从命令行删除Nuget缓存
• 我能找到的所有其他建议都可以作为StackOverflow上的解决方案

无论我做什么，它仍然显示错误的版本，因此，当应用程序运行时，由于正确的版本是本地复制的，因此会引发异常。

谁能建议我如何解决这个问题？

编辑：

软件包配置：

<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="BouncyCastle" version="1.8.5" targetFramework="net452" />
  <package id="JetBrains.Annotations" version="2019.1.3" targetFramework="net452" />
  <package id="MailKit" version="2.4.1" targetFramework="net452" />
  <package id="MimeKit" version="2.4.1" targetFramework="net452" />
</packages>

项目文件（仅引用MailKit和MimeKit，其余部分均删除为不必要，让我知道是否需要更多内容）：

<Reference Include="MailKit, Version=2.4.1, Culture=neutral, PublicKeyToken=4e064fe7c44a8f1b, processorArchitecture=MSIL">
  <SpecificVersion>False</SpecificVersion>
  <HintPath>..\packages\MailKit.2.4.1\lib\net45\MailKit.dll</HintPath>
</Reference>
<Reference Include="MethodExtensions, Version=1.0.4469.11621, Culture=neutral, processorArchitecture=MSIL">
  <SpecificVersion>False</SpecificVersion>
  <HintPath>..\..\Libraries\MethodExtensions\bin\Debug\MethodExtensions.dll</HintPath>
</Reference>
<Reference Include="MimeKit, Version=2.4.1, Culture=neutral, PublicKeyToken=bede1c8a46c66814, processorArchitecture=MSIL">
  <SpecificVersion>False</SpecificVersion>
  <HintPath>..\packages\MimeKit.2.4.1\lib\net45\MimeKit.dll</HintPath>
</Reference>

进一步编辑：

为了澄清起见，该软件包安装的dll版本显然是2.4.1：

Here is the runtime error message confirming that it is looking for 2.4.0 which is no longer on the computer following the Nuget update:

The Solution

The answer from @zivkan pointed me in the right direction. Firstly I was looking for entirely the wrong thing, assuming that the version in the Property Grid was incorrect when in fact it was perfectly fine. The reference is located in a plugin module which itself compiles to a library, which means that when compiling the MailKit dll not only has to be copied local but then copied to the main application folder using a post build event command line. It turns out that there was an error in the post build event code so that MailKit was not copied and MimeKit was copied twice. Not taking the blame for that one, but I do take the blame for not recognising the problem!

Thanks, @zirkan, for your help and explanation which finally got me to the resolution...