You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed before that none of the 17 obj dirs are ever being cleaned, which on some occasion caused me problems. They usually contain both Release and Debug subdirs with often some files directly in obj. Thinking about a fix, it is not clear which target should clean them. Maybe a new target clean-all?
I guess part of the question is how much cleaning is expected of "clean". Like if you create a brand new .NET console program then run dotnet build and dotnet clean there's still a lot of stuff left over in the obj folder. Anyway, if we want to force clean everything maybe it could be called purge?
The impact of this issue has been reported in #1422 (comment) and #1433. Below is a copy of the discussion under #1433 about a possible solution.
Ok, managed to reproduce the failure. I think there might be a few issues:
[...]
msi\obj
is not getting cleaned? Somehow I managed to hit the same issue you had and zapping this folder "fixed" the issue.Originally posted by @slozier in #1433 (comment)
I have noticed before that none of the 17
obj
dirs are ever being cleaned, which on some occasion caused me problems. They usually contain bothRelease
andDebug
subdirs with often some files directly inobj
. Thinking about a fix, it is not clear which target should clean them. Maybe a new targetclean-all
?Originally posted by @BCSharp in #1433 (comment)
I guess part of the question is how much cleaning is expected of "clean". Like if you create a brand new .NET console program then run
dotnet build
anddotnet clean
there's still a lot of stuff left over in theobj
folder. Anyway, if we want to force clean everything maybe it could be calledpurge
?Originally posted by @slozier in #1433 (comment)
The text was updated successfully, but these errors were encountered: