[Actions] Redesign the Windows build to automatically find the proper devenv#339
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the Windows GitHub Actions workflow to locate Visual Studio’s devenv dynamically at runtime instead of relying on a hard-coded path, improving portability across runner images/VS editions.
Changes:
- Removed the hard-coded
devEnvpath from workflowenv. - Added a
vswhere-based discovery step to determine the Visual Studio install path and derivedevenv. - Simplified repeated per-project build commands into a
forloop to reduce duplication.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
sebaszm
approved these changes
Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.