Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

error MSB3021: Unable to copy file

See original GitHub issue

/usr/share/dotnet/sdk/2.0.2/Sdks/Microsoft.NET.Sdk/build/Microsoft.NET.Publish.targets(109,5): error MSB3021: Unable to copy file . . .
. . . . Could not find a part of the path  .  . .

# dotnet --info
.NET Command Line Tools (2.0.2)

Product Information:
 Version:            2.0.2
 Commit SHA-1 hash:  a04b4bf512

Runtime Environment:
 OS Name:     debian
 OS Version:  9
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /usr/share/dotnet/sdk/2.0.2/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

Issue Analytics

State:
Created 6 years ago
Comments:11 (2 by maintainers)

Top GitHub Comments

1reaction

Eshvacommented, Nov 29, 2017

@alvarollmenezes Just delete bin/Debug/ folder(s) before you build .NET Core assemblies. In my case I build using npm script and the script looks like this: "build:linux:service:dev": "rm -r -f ../bin/deb/core/linux-x64/ && dotnet publish ../EveHQ-NG.sln --runtime linux-x64 --configuration Debug --self-contained", You can see it in this file: project.json

0reactions

mbpcommented, Oct 3, 2018

I experienced this problem as well, and solved it by using correct casing for filenames

E.g. there was a folder wwwroot/Scripts but tsconfig.json had "outFile": "wwwroot/scripts/foo.js". Changing the outfile directory to capital S fixed it.