Issue with boilerplate framwork unit testing

Question

0.00/5 (No votes)

See more:

Hi,

Presently i am working with boilerlate framework, while doing unity testing i am getting below error.

Message: System.IO.FileLoadException : Could not load file or assembly 'Microsoft.Extensions.DependencyInjection.Abstractions, Version=1.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

please help me out of this.

Thanks in advance.

What I have tried:

Actually i have no idea about unit test cases. so i did not tried anything.

Posted 6-Sep-17 0:13am

Lokesh Rajana

Updated 6-Sep-17 0:44am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pete O'Hanlon · Accepted Answer · 2017-09-06T00:44:00

The problem you have here has nothing to do with the unit tests, per se. The problem is that you either don't have Microsoft.Extensions.DependencyInjection.Abstractions referenced in your unit test assembly, or a dependency of this assembly is missing, or you have the wrong version of this assembly referenced by your unit test assembly. What is happening here is that, even though your unit test doesn't have any code that calls into this assembly (hence the reason your unit test compiles) but it's relying on it being there because your actual code is looking to use it. As this is from a nuget package, all you need do is add exactly the same nuget reference to your unit test assembly as you have in your main project.