Problem of AutoFixture current version with Moq current version

[binydev]

when i build my application using Team Foundation MsBuild I face this problem. it work on my local computer I face this problem when it is on server.

System.IO.FileLoadException: Could not load file or assembly 'Moq, Version=3.1.416.3, Culture=neutral, PublicKeyToken=69f491c39445e920' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at Ploeh.AutoFixture.AutoMoq.MockPostprocessor.Create(Object request, ISpecimenContext context)

[moodmosaic]

Could you try to add binding redirects to the config file via NuGet (or manually)?

[binydev]

Ya I know.. on my local computer build it works... but on deployment it doesnt!

[ploeh]

Are you using the same test runner on your local computer and the build server, or is it two different test runners?

[binydev]

I use the same. I use visual studio 2012 on my local computer and TFS 2012 on server. we configure automated build and deployment on test server. and when I trigger build it show me the following error.

Test method NeoplexERP.Service.Business.UnitTests.Core.LookupBusinessService_GetAllTest.Should_GetAll_Gender threw exception:
System.IO.FileLoadException: Could not load file or assembly 'Moq, Version=3.1.416.3, Culture=neutral, PublicKeyToken=69f491c39445e920' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at Ploeh.AutoFixture.AutoMoq.MockPostprocessor.Create(Object request, ISpecimenContext context)

[ploeh]

I don't know how TFS works, but from the exception message, it's quite clear that it can't find Moq, so either it's not picking up the assembly redirect, or the file is not available on the server.

If you can provide a way to reproduce the issue (without asking us to install TFS), we can take a look, but otherwise, this sounds like a TFS issue rather than an AutoFixture issue.

[binydev]

No no... it is not related to TFS issue! there is Moq.dll on build folder but it is version 4.0... in my local computer the same I have only version 4.0... but it show me this error message when it is on build server! why is that...?

[moodmosaic]

How TFS invokes MSBuild? What are the arguments supplied to the MSBuild.exe process?

[binydev]

we give arguments on build definition! and MSBuild.exe will be called with those configuration

[adamchester]

Can you post the full build log somewhere? (Not here, just give us the URL).

[ploeh]

There's not a lot of detail to go with here.

It may be true that the issue isn't related to TFS, but if that's the case, you should be able to tell us how to reproduce the issue.

Right now, based on my experience, the error message you're seeing is always caused by a problem with assembly redirects. Either the assembly redirect is incorrect, or the test runner isn't picking it up. Keep in mind that having an app.config file associated with a library (.dll) isn't picked up the .NET run-time by default, so it's something every test runner explicitly does.

[binydev]

@ploeh I agree with your approach... due to the TFS build copy only one version of Moq (4....) unable to redirect to the exact version. my point is I remove version Moq(3.6...) on my local computer and I run the test project it work fine... why no it does not work on other machine? "Ploeh.AutoFixture.AutoMoq.MockPostprocessor.Create" does not request version 3.6... why it use version 4?

[ploeh]

@bcopmt143 Were you able to resolve your issue?

[ploeh]

Closing due to inactivity.

[Skm5900]

Hi Team,
Same issue facing here, unit test having reference to AutoFixture is not working for below line of code on devOps pipeLine build, on local it works fine. Please sugggest.

[aivascu]

@Skm5900 It might be that you are relying on the implicit version of Moq added by AutoFixture.AutoMoq.
The Moq version in our packages is intentionally kept at lower values to enable more compatibility.
You should install Moqpackage in your test projects and update it to the latest version.