Visual Studio refuses to build project due to missing assembly reference that isn't missing

62,422

Solution 1

1.remove all references

2.Build --> Clean solution

3.Clean your project using this project as sometimes visual studio fails to clean everything neatly.

Solution 2

In my case, target Framework of Assembly Project and the target Framework of the project where i want to use this assembly are different. Target framework of assembly project was 4.5 and target framework of my project was 4.0.

When I have change the target framework of my project to the target framework of assembly project i.e. from 4.0 to 4.5 , it works fine.

For change the Target Framework of project,

Right Click the project -> Properties -> Application -> Target Framework

This Target Framework is drop-down list, select your required Framework from this list.

Solution 3

Reinstalling packages worked for me.

From the Package Manager Console, run the the following command to reinstall all packages.

update-package -reinstall

You can target a single package with:

update-package PACKAGE_NAME -reinstall

Solution 4

Another possible issue could be mismatch in targeted versions of .NET between the assemblies. I experienced the same symptoms and setting the same version of framework did the trick for me.

Solution 5

I think you are missing a Nuget Library called: Bogus. You can install it from Nuget-Solution installer in visual studio. Just install it and also add using Bogus.DataSets; on your class file. Hopefully this will solve your issue.

Share:
62,422
user1531921
Author by

user1531921

Updated on January 27, 2022

Comments

  • user1531921
    user1531921 over 2 years

    I'm building a c# windows service and has added a couple of assembly references (to other projects of my own) to my project.

    I get the following error when I build:

    "Error 25 The type or namespace name 'TestClass' could not be found (are you missing a using directive or an assembly reference?"

    Interestingly enough, the reference path in the csproj-file is correct, and on top of that, classes and namespaces from the referenced project, that according to Visual Studio is missing, is being picked up by Intellisense and even the "go to definition" function works fine. Furthermore, I have other projects in the exact same folder as my new windows service and they picked up the assembly references just fine. All the referenced projects are included in the solution.

    I use Visual Studio 2013 Update 3. There is really no code that I could show that would give you more information, but let me know if you want to see some screenshots or something.

    Attempts so far:

    Update When I select one of the "missing" references in the reference list, and go to properties, there is no path defined. Yet, the relative path is in the csproj-file as is correct. Confusing.

    Update 2 Removing all the references, reloading the projects and then doing a clean fixed it for me. Apparently, the problem was caused by all dlls not being updated in the build stack.

  • user1531921
    user1531921 about 9 years
    I tried removing every single reference, then did a clean. It seems to have done the trick. Thanks!
  • user1531921
    user1531921 about 9 years
    I have to wait a couple of minutes before I can accept it. I will when I can.
  • chris c
    chris c over 4 years
    If you received a solution from a 3rd party, check your solution and the 3rd party solution are the same .net framework versions. Was my problem and a simple change of version did the trick