# docs: Add note to Windows building docs \(\#60104\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/779ca5ef7248b1f66bad91f85a5c5d0b6922de6e)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 779ca5ef7248b1f66bad91f85a5c5d0b6922de6e

Requested commit: 779ca5ef7248b1f66bad91f85a5c5d0b6922de6e

Commit: 779ca5ef7248b1f66bad91f85a5c5d0b6922de6e

Tree: 557c5ce9bc8325826bbccf56e0437733fece53a2

Author: Yue Fei

Committer: GitHub

## Message

```
docs: Add note to Windows building docs (#60104)

# Objective

Microsoft has decoupled the MSVC version from the Visual Studio version
starting with Visual Studio 2026 (see [this
blog](https://devblogs.microsoft.com/cppblog/new-release-cadence-and-support-lifecycle-for-msvc-build-tools/)),
meaning that the previous traditional naming conventions were obsolete.
For Visual Studio 2026 (including future newer versions of VS) users,
the existing docs will probably confuse them, as they cannot find out
the components named like "MSVC v145 - VS 2026 C++ ..." in present
Visual Studio Installer.

## Solution

Add a note next to the dependencies.

## Testing

Docs are no need to test. (Maybe?)

## Self-Review Checklist:

- [x] I've reviewed my own diff for quality, security, and reliability
- [x] Unsafe blocks (if any) have justifying comments
- [x] The content adheres to Zed's UI standards
([UX/UI](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist)
and
[icon](https://github.com/zed-industries/zed/blob/main/crates/icons/README.md)
guidelines)
- [x] Tests cover the new/changed behavior
- [x] Performance impact has been considered and is acceptable

Release Notes:

- N/A
```

## Parents

- [f964172a69779353853b7aa63c944c9fa680ab7e](https://git.cafe/gitcafe/zed/commit/f964172a69779353853b7aa63c944c9fa680ab7e?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/779ca5ef7248b1f66bad91f85a5c5d0b6922de6e?format=markdown)