Container.Should().Have() Is not found. about fluentassertions.autofac

[stephenpatten]

Promise I will get to this as soon as I get settled into my new house and job (sort of).

[mkoertgen]

Hi @stephenpatten,
You're right. It looks like the compiler can only resolve the FluentAssertions core extensions but not the AutoFac-specific ones. Note that they live in the namespace FluentAssertions.AutoFac.

Be sure to add using FluentAssertions.Autofac; after using FluentAssertions; at the top of your Test classes to help the compiler find the IContainer-extension methods.

Let me know if that helps.

[stephenpatten]

Thanks for the quick response.

As a sanity check I have forked FluentAssertions.Autofac and can get the repo to build on the same machine that is having issues with adding the reference to fluentAssertions.Autofac. Here are some images that might help use diagnose the issue. The UnitTest project is targeting 4.5.2

[mkoertgen]

Hm, i would need to guess. The indicated versions should be compatible.

Looks like something simple & stupid. It seems the package reference somehow got messed up.

However, 4.5.2 should be ok. Did you probably tweak the target framework after adding the NuGet reference?

Did you try building with maximum verbosity and check the output on messages with respect to the reference?

If that does not help, would it be possible for you to publish the solution in a manner that i could possibly reproduce the error?

[stephenpatten]

How can I give it to you in a secure way?

[stephenpatten]

Setting the build output did not shed any light on the issue, BUT if I removed the nuget package for the test project and then added the dll by hand it works... weird

[mkoertgen]

For me to reproduce you could clone/upload it to a private repo and add me as a team member. GitLab.com has free private/personal repos, for instance.

Another guess: Did you try moving the using clauses out of your own namespace and to the top of file?

[mkoertgen]

Close due to inactivity