-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Add VS Professional and VS Enterprise configurations #5515
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small nits to be consistent with PowerToys / terminal repo, and for a better UX in the configuration output
@@ -24,7 +24,9 @@ | |||
## Building the client | |||
|
|||
1. Clone the repository | |||
2. Configure your system using the [configuration file](../.config/configuration.winget) in the repository. To run the configuration, use `winget configure .config/configuration.winget` from the project root so relative paths resolve correctly. | |||
2. Configure your system using the [configuration file](../.config/configuration.winget) in the repository. To run the configuration with VS Community, use `winget configure .config/configuration.winget` from the project root so relative paths resolve correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I think the Community version would better be in the list alongside the Pro and Enterprise version
- For Community ...
- For Pro ....
- For Enterprise ...
Closes #5514
The configuration files are identical to the original save for the VS edition.
Tested using VS Enterprise on two machines.
Microsoft Reviewers: Open in CodeFlow