benagain / nsubstitute.verify.that Goto Github PK

I use FluentAssertions 5.6 and NSubstitute 4.1, but there is exception about type loading.

System.TypeLoadException: Could not load type 'NSubstitute.Core.Arguments.ArgumentSpecificationQueue' from assembly 'NSubstitute, Version=4.1.0.0, Culture=neutral, PublicKeyToken=92dd2e9066daa5ca'.
at NSubstitute.Verify.That[T](Action`1 action)

Hi, I have recently stumbled across this project, and was very keen to try applying FluentAssertions to NSubstitute verifications, but I am getting the following error when I try to run my tests:

System.IO.FileLoadException : Could not load file or assembly 'NSubstitute, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. 
The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I have tried adding assembly binding redirects for NSubstitute as follows:

<dependentAssembly>
  <assemblyIdentity name="NSubstitute" publicKeyToken="92dd2e9066daa5ca" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
</dependentAssembly>

I am using NSubstitute 4.2.0 and FluentAssertions 5.7.0 with NUnit 3.12.0, and my application and tests are all based on .NET Framework 4.7.2. All my tests that don't use the Verify.That code pass, and if I rewrite my failing tests to not use Verify.That either then they pass.

Is there anything obvious that I am missing?

At least a minimal example on how the library is intended to be used as a quick-starter.

You have a reference in code, but that is not enough. Here is a good doc guide IMHO: https://diataxis.fr/

Why should I use this lib instead of https://github.com/PapGroup/NSubstitute.FluentAssertionsBridge?

reverse question: PapGroup/NSubstitute.FluentAssertionsBridge#1

Hi there, I'm trying to use your library with .net core 2.1 project that depends on FluentAssertions 5.0+ and it looks like it just causes the test to fail 100% of the time with NSubstitute thinking there's no matching calls.

However if I bring the Verify class into the project it seems to work perfectly fine. Feels like a weird .net dependency issue.

Are there any plans to update to 5.0+ of FluentAssertions?