title: RedundantNameQualifier error when Running Resharper CLI inspect tool
body: <p>I'm using Resharper inspect CLI tool for static code analysis(JetBrains.ReSharper.CommandLineTools.2018.3.1\InspectCode.exe) on a dotnet core 2.1 console application I've created.  Within the solution, there is a separate project which is just a package used in the console app.  </p>
  
  <p>Layout is as follows:</p>
  
  <p><a href="https://i.stack.imgur.com/1GLXa.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/1GLXa.png" alt="enter image description here"></a></p>
  
  <p>When I run the inspectCode.exe as follows:</p>
  
  <pre><code>JetBrains.ReSharper.CommandLineTools.2018.3.1\InspectCode.exe "AI.DL.Backup\AI.DL.Backup.csproj" /o:"CodeInspection_20222.xml" /profile:"AI.DL.Backup.sln.DotSettings"
  </code></pre>
  
  <p>I get the following issue:</p>
  
  <p><a href="https://i.stack.imgur.com/mRDU4.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/mRDU4.png" alt="enter image description here"></a></p>
  
  <p>Output xml report has the following:</p>
  
  <pre><code>&lt;IssueType WikiUrl="https://www.jetbrains.com/resharperplatform/help?Keyword=RedundantNameQualifier" Severity="WARNING" Description="Redundant name qualifier" CategoryId="CodeRedundancy" Category="Redundancies in Code" Id="RedundantNameQualifier"/&gt;
  
  &lt;Issue Message="Qualifier is redundant" Line="5" Offset="146-154" File="AI.DL.Backup\src\AI.DL.Backup\Startup.cs" TypeId="RedundantNameQualifier"/&gt;
  </code></pre>
  
  <p>The problem seems to be that it cannot find the dll project referenced and is throwing code analysis error (code HAS been built already, so bin/obj folders exist with relevant dlls/packages required).</p>
  
  <p>Ling 5 (as specified) is just the using statement for the separate package, which it cannot resolve and is deeming to be redundant.</p>
  
  <pre><code>using AI.DL.DocumentManagement;
  using AI.DL.DocumentManagement.Stores;
  </code></pre>
  
  <p>Going by the generated XML report, I can see that it can't find the namespace within the separate package.  Why would this be?  Anyone seen this before?</p>