Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove check for dotnet.exe from startvs.cmd. #856

Merged
merged 1 commit into from
Nov 16, 2023

Conversation

mitchdenny
Copy link
Member

This check is not helpful. At points in time where we are running against stable bits (like 8.0.100 RTM) the .\restore.cmd script won't actually install a repo local copy of .NET, and so this path will never exist. We may as well ditch the check.

@mitchdenny mitchdenny merged commit eb91c2d into main Nov 16, 2023
3 checks passed
@mitchdenny mitchdenny deleted the remove-dotnet-path-check branch November 16, 2023 05:15
@RussKie
Copy link
Member

RussKie commented Nov 16, 2023

The check guards against attempts to start VS without restoring the toolset first. The change also presumes .NET 8 is installed globally, which is not necessarily the correct assumption.

@mitchdenny
Copy link
Member Author

mitchdenny commented Nov 16, 2023

Unfortunately restore.cmd assumes that if it is installed globally it doesn't need to install it locally. Which means right now, with 8.0.100 being what we are using in the repo, startvs.cmd is broken. If we are going to have a check it needs to be able to work regardless of where we are in the release lifecycle.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants