title: dotnet run --project <PATH> not taking project path as working directory
body: <p>When using the .NET commands to run my Console App that is being stored on a network drive it sees the Working Directory as where it is being called from instead of the project path..</p>
  
  <p><code>dotnet run --project "\\network.drive\path\example\project"</code></p>
  
  <p>I get the output as follows:</p>
  
  <pre><code>WORKING DIRECTORY: C:\Windows\system32
  Current Environment: DEV
  Current Root URL: &lt;API_URL&gt;
  Current Excel File:
  
  Unhandled Exception: System.ArgumentNullException: Value cannot be null.
  Parameter name: fileName
     at System.IO.FileInfo..ctor(String originalPath, String fullPath, String fileName, Boolean isNormalized)
     at System.IO.FileInfo..ctor(String fileName)
     at MyProject.Reader.ReadAgentData(Int32 sheetIndex) in \\network.drive\path\example\project\Reader.cs:line 68
     at MyProject.Program.Main(String[] args) in \\network.drive\path\example\project\Program.cs:line 119
  </code></pre>
  
  <p>The error is the Excel File variable being an empty string. Since the working directory is not the path of the project, but instead <code>C:\Windows\system32</code> it cannot find the appsettings.json file that the information is pulled from.</p>
  
  <p>Weirdly enough, using the command <code>dotnet watch --project "\\network.drive\path\example\project" run</code> causes the process to run correctly, it has the correct working directory and reads the appsettings.json file without issues, but then it obviously has to wait for a file change (the purpose of watch)..</p>
  
  <p>How can I have my app recognize the Working Directory as the root of the project folder when using <code>dotnet run --project</code>?? (To be clear, I do NOT want to use watch unless I can have it end automatically)</p>