[WatchDog]

The license doesn't actually permit OSS development. Only compilation of near-unmodified third party OSS libraries.

You may not compile OSS software developed by your own organisation.

The OSS software must be unmodified, "except, and only to the extent, minor modifications are necessary so that the Open Source Dependencies can be compiled and built with the software."

https://visualstudio.microsoft.com/license-terms/vs2026-ga-d...

[dwattttt]

Using VS build tools for open source development is covered by the Community licence [0], separate from this Build Tools licence change. That license is more open than you might expect, working as an individual it even permits proprietary development for commercial purposes.

Under that usage, the Community license counts as a valid Visual Studio license for Build Tools purposes, hence the second paragraph:

> This change expands user rights to the Build Tools and does not limit the existing Visual Studio Community license provisions around Open-Source development. If you already are a developer contributing to OSS projects, you can continue to use Visual Studio and Visual Studio Build Tools together for free, just like before.

[0] https://visualstudio.microsoft.com/license-terms/vs2022-ga-c...