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
Currently, the Clean target ends up triggering a read of the assets file if it exists.
This is due to the following competing concerns:
Assets file resolution is responsible for populating transitive project references
Transitive project references must be added before AssignProjectConfiguration
Clean must run AssignProjectConfiguration in order to clean referenced projects
We don't need the transitive project references to clean, but the problem is that once AssignProjectConfiguration is run, it won't re-run if there's a subsequent invocation of the Build task.
We have some code to special case clean, and it is smart enough to not kick in if the build is triggered by /t:rebuild, but not if /t:build;clean is used.
Issues with /t:Clean;Build
When there has not been a prior restore, it will not trigger "assets file is missing, run restore", but instead resolve no assets and move on to compilaton that will fail to resolve anything.
It will hide all assets log messages
So to be clear, this issue tracks two related things:
/t:Clean;Build should work the same as /t:Rebuild and /t:Clean in all cases.
/t:Clean alone should never read the assets file
The text was updated successfully, but these errors were encountered:
Currently, the Clean target ends up triggering a read of the assets file if it exists.
This is due to the following competing concerns:
We don't need the transitive project references to clean, but the problem is that once AssignProjectConfiguration is run, it won't re-run if there's a subsequent invocation of the Build task.
We have some code to special case clean, and it is smart enough to not kick in if the build is triggered by /t:rebuild, but not if /t:build;clean is used.
Issues with /t:Clean;Build
So to be clear, this issue tracks two related things:
The text was updated successfully, but these errors were encountered: