title: Visual Studio is looking for an old Nuget Package with no publicKeyToken
body: <p>I have a Nuget package in my project which was previously unsigned and did not have a strong name.</p>
  
  <p>I've released a new version of the package which is now signed.</p>
  
  <p>When I add the new version of my Nuget package to my solution, anywhere within the project that references an assembly from the Nuget package, causes the following build error:</p>
  
  <blockquote>
    <p>Error CS0012  The type 'JsonWebToken' is defined in an assembly that is
    not referenced. You must add a reference to assembly
    'TSC.Business.DataContracts, Version=2.10.6.0, Culture=neutral,
    PublicKeyToken=null'.</p>
  </blockquote>
  
  <p>As you can see, the compiler is still expecting a version of the assembly which has no PublicKeyToken.</p>
  
  <p>I need to try and identify why the compiler is still expecting the publicKeyToken for this package to be null. </p>
  
  <p>Things I've tried - all with no luck:</p>
  
  <ul>
  <li><p>Completely uninstalling the old Nuget package by removing the old version from the packages.json, the packages directory, the csproj file, the bin path and running a full clean.</p></li>
  <li><p>Validating that the publicKeyToken of the new version is correct in the packages.json - it is</p></li>
  <li><p>Clearing my temporary ASP.Net files</p></li>
  <li><p>Heck, even installing VS2019 and checking if the problem exists in there - which it does</p></li>
  </ul>
  
  <p>Does anybody know where else the compiler could be looking for this null publicKeyToken?</p>