Need a work around Microsoft.QualityTools.Testing.Fakes

Question

We been getting this on are most up to date systems VS 12 update 4 we have tried setting specific version to false and still get the test failing with this message

Product.Business.Test.Providers.AuthenticationProvider.GivenRequestToStoreAuthenticationState_WhenParametersAreValid.ThenItShouldStoreTheAuthenticationState threw exception: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.QualityTools.Testing.Fakes, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

can anybody save us from this fake calamity

this [answer](http://stackoverflow.com/a/31941344/1257607) solved it for me — DanielV, Aug 11 '15 at 12:18

score 7 · Answer 1 · answered Jan 08 '15 at 07:37

7

This solved it for me:

deleting the bin, obj and FakesAssemblies folder
make sure the specific version for the Microsoft.QualityTools.Testing.Fakes assembly is set to 'false'
rebuild the test project

answered Jan 08 '15 at 07:37

Stef Heyenrath

9,335
12
66
121

score 4 · Accepted Answer · answered Jan 02 '15 at 14:49

4

I was getting a similar issue some time back. Re-referencing the test assembly and recreating the Fakes assembly sorted the issue for me.

answered Jan 02 '15 at 14:49

sethidev

111
5

Thanks this seamed to fix it i'm very gratful had spent about 3 hours fighting though many other ways that just did not work – TechLiam Jan 02 '15 at 21:45
You saved my n number of hours! Thanks. – SarjanWebDev May 29 '15 at 04:57

score 2 · Answer 3 · edited May 03 '16 at 14:39

After days of fighting this problem in TFS Build, I discovered it is really a runtime error when the unit tests are run by TFS. The key is "or one of its dependencies." The

Microsoft.QualityTools.Testing.Fakes.dll

is dependent on

Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll

so I copied the framework DLL into the Fakes directory and checked it in. That solved the problem.

score 1 · Answer 4 · edited Nov 07 '17 at 12:35

1

Adding the below entry in App.config worked for me.

<runtime> 
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
   <dependentAssembly> 
     <assemblyIdentity name="Microsoft.QualityTools.Testing.Fakes" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/> <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="12.0.0.0"/> 
    </dependentAssembly> 
   </assemblyBinding> 
</runtime>

edited Nov 07 '17 at 12:35

bummi

27,123
14
62
101

answered Nov 07 '17 at 12:29

Samatha Boini

11
1

The project that was giving me trouble had that entry in the app.config, only the newVersion which was supposed to be 12.0.0.0 was set to 11.0.0.0 causing half my tests to fail. – Rich Jan 15 '19 at 22:22

Need a work around Microsoft.QualityTools.Testing.Fakes

4 Answers4