Skip to content

Avoid UsingTask when the target does not exist#42238

Merged
jjonescz merged 1 commit intodotnet:mainfrom
jjonescz:tearing-conditional
Jul 18, 2024
Merged

Avoid UsingTask when the target does not exist#42238
jjonescz merged 1 commit intodotnet:mainfrom
jjonescz:tearing-conditional

Conversation

@jjonescz
Copy link
Copy Markdown
Member

@jjonescz jjonescz commented Jul 18, 2024

@ghost ghost added Area-Infrastructure untriaged Request triage from a team member labels Jul 18, 2024
@jjonescz jjonescz marked this pull request as ready for review July 18, 2024 16:55
Copy link
Copy Markdown
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My only concern here is the silent fallback to previous (bad) behavior if restore is done outside of VS and then VS doesn't retrigger restore. This definitely seems like an improvement.

@jjonescz
Copy link
Copy Markdown
Member Author

My only concern here is the silent fallback to previous (bad) behavior if restore is done outside of VS and then VS doesn't retrigger restore.

If we follow up with #42216 there will be no silent fallback (we will instead report an error if we cannot find the package during compilation).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Infrastructure untriaged Request triage from a team member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants