[quietbritishjim]

That just confirms the parent comment's point. If you're just using the build tools directly, you're fine. If need to develop "with Visual Studio" i.e. the IDE, not just the command line tools, then you need the paid license.

[dwattttt]

It's actually not. It's complicated, but they're explicitly allowing Build Tools to be used to compile open source dependencies of closed source projects that do not need the MSVC toolchain for proprietary components.

It's why the example they give in the article is a Node.js application with native open source dependencies (e.g. sqlite3).

EDIT: it's clearer when read in context of the opening paragraph:

> Visual Studio Build Tools (VSBT) can now be used for compiling open-source C++ dependencies from source without requiring a Visual Studio license, even when you are working for an enterprise on a commercial or closed-source project.

[quietbritishjim]

Ok that does sound a bit different.

[dwattttt]

I wish the post was clearer (though I'm not sure what that looks like). I've made the same mistake interpreting it, then had to go back and reread it a few times.