6

I have run into a strange issue in Visual Studio 2017. Recently a change in our internal nuget packages moved a class, that is used in an extension, to another project/package, but the namespace was not changed. Upon updating the new packages in another solution the extension methods began all throwing compile errors.

"Reference to type 'x' claims it is defined in 'y', but it could not be found"

I can get the solution to build by, changing the extension method to be used as static invocations, using Visual Studio 2013, or having resharper build use msbuild 12 (14 and 15 throw the same error).

I have tried clearing cache, deleting packages and restoring, restarting everything, and a fresh checkout in a separate folder. Also looked at other questions that had the same error, but nothing they mentioned worked.

I do plan to make the team that moved the class to fix the namespace to match the project, but it will take a few weeks to get it through.

Ex:

//In project Company.Auto 
namespace Company.Auto.Extensions
{
   using System;

   public static class Cars
   {
       public static IDictionary<string, Car> DoStuff(this Car car)
       {
       }
   }
}

//Moved to project Company.Stuff.Something.Documents
namespace Company.Auto.Domain
{
   using System;

   public class Car
   {

   }
}
Joy
  • 1,171
  • 9
  • 15
Joshua5822
  • 341
  • 2
  • 10
  • Does this answer your question? [VS2015 C# interactive: error CS7069: Reference to type 'Object' claims it is defined in 'System.Runtime', but it could not be found](https://stackoverflow.com/questions/36723359/vs2015-c-sharp-interactive-error-cs7069-reference-to-type-object-claims-it-i) – Jim G. Sep 08 '22 at 11:55

1 Answers1

0

I had the same issue, I rebuilt each library referenced by the offending application individually which seems to have fixed the problem. Seems like some sort of caching issue.

Gary Mason
  • 9
  • 1