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.

[2.1-rc1] dotnet clean fails when obj folder is missing

See original GitHub issue

How to reproduce

Run dotnet new classlib in an empty folder
Delete the obj folder
Run dotnet clean

What happens

Clean fails
obj folder is created with empty folders

What should happen

Nothing, project is already clean

This is an issue on our CI server, where we run dotnet clean as the first step of every build, and then run dotnet restore as the second step. It now fails on the initial build, when it clones the repo and there is no obj folder.

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:10 (7 by maintainers)

Top GitHub Comments

2reactions

gceletcommented, May 11, 2018

thanks for this quick fix: waiting the next release to test it. great work @nguerrera

0reactions

nguerreracommented, May 10, 2018

@Petermarcu TBD I suppose, but it is a regression and pretty bad. I’m doing some validation and will send to ship room this afternoon for the call.

Top Results From Across the Web

Project file is incomplete. Expected imports are missing

After this I've reinstalled the dotnet-sdk-2.1. 200-win-x64 package and everything worked fine. Deleting the bin and obj folders for the ...

Project file is incomplete. Expected imports are missing-.net-core

After this I've reinstalled the dotnet-sdk-2.1. 200-win-x64 package and everything worked fine. Deleting the bin and obj folders for the project fixed this...

https://dev.azure.com/dotnet/fe18572b-d1ba-496a-9e...

... 2.1-rc1 -> 2.1-rc1 2020-12-03T13:33:19.1815774Z * [new tag] 2.1-rc2 -> 2.1-rc2 ... dotnet\sdk\3.1.404\Sdks\NuGet.Build.Tasks.Pack\buildCrossTargeting\NuGet ...

No object (name: request) has been registered for this thread

I'm getting this error message when running my tests: ERROR: Failure: TypeError (No object (name: request) has been registered for this ...

Correct Caching is always hard - Scott Hanselman's Blog

NET Core 2.1 RC1. First, .NET Core 2.1's Release Candidate is out. This one has a Go Live license and it's very close...