microsoft / microsoft/VbsEnclaveTooling
Fix CI Build on vs 2026
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 28
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
CI build on VS 2026 failed. Came to our attention in #205 . This issue tracks a fix to make sure we can 2026 in the future.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #205 and locating the CI configuration or job that failed on VS 2026. Confirm the failure and identify the required build change; done means the CI build succeeds on VS 2026 and continues to support the relevant future build path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100