CODEWITHSUNDEEP
c#.netvisual-studiowindows-servicesassembly-references
user1531921
user1531921

Reputation: 1432

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

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.

Upvotes: 36

Views: 77227

Answers (7)

srk
srk

Reputation: 1901

I faced a similar issue: the compiler complained about a missing assembly reference, even if it was in the csproj file.

Error without the reference:

error CS0246: The type or namespace name 'IMyService' could not be found (are you missing a using directive or an assembly reference?)

So I added the reference:

<Reference Include="My.Library, Version=1.0.0.0, Culture=neutral, processorArchitecture=MSIL">
  <SpecificVersion>False</SpecificVersion>
  <HintPath>path/to/lib/My.Library.dll</HintPath>
</Reference>

And got a slightly different error:

error CS0012: The type 'IMyService' is defined in an assembly that is not referenced. You must add a reference to assembly 'My.Library, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'.

Even after updating the reference to match the exact string from the error message, I still got that second error.

The problem was that I was mixing signed and unsigned assemblies. My project architecture was roughly this:

  • A.dll - unsigned assembly
  • B.dll - signed assembly; references A.dll; compiles OK
  • C - references A.dll and B.dll; individual references OK; get errors above when calling a method in B that returns a type from A

I fixed my issue by signing the assembly ("A" in my example above). I did this by referencing the StrongNamer NuGet package.

Upvotes: 0

Liakat Hossain
Liakat Hossain

Reputation: 1364

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.

Upvotes: 2

Ryan Varley
Ryan Varley

Reputation: 423

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

Upvotes: 9

Iizuki
Iizuki

Reputation: 410

I the same problem. Or at least the symptoms were same. My solution was located on a network drive. Moving the solution to my local drive solved the problem for me.

The reason was apparently that Windows 10 didn't see the network drive as a trusted enough location. It worked fine until I managed to break my solution somehow. Visual studio apparently didn't have the required rights to perform needed the fixing operations.

Upvotes: 0

nayef harb
nayef harb

Reputation: 753

1.remove all references

2.Build --> Clean solution

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

Upvotes: 14

mayank
mayank

Reputation: 2665

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.

Upvotes: 37

zmaten
zmaten

Reputation: 477

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.

Upvotes: 4

Related Questions