But the preferred form for modification includes being able to test your changes. Source without installation scripts is most likely not the preferred form - ie what do engineers at the company use?
> if I open source a .NET project that doesn't mean it has to include Visual Studio, which is the preferred way to build it
Yes, because having been designed in the era of expensive compilers, GPL2 explicitly covers this:
> However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable
You're trying to draw a box around "Windows" and define operating system as everything in that box. But minesweeper is not an operating system component, it's just something that comes with Windows. A hypervisor is an operating system component, even though not all versions of Windows have one.
So is a compiler.
I imagine there exist developer-oriented PC OEMs that offer PCs with Windows and Visual Studio already installed. So then it is included with the OS by the OEM. The fact that that would change the outcome in your interpretation implies that there is something wrong with it.
That in practice nobody except FSF and Debian cares is another thing.
In short: yes.
Being able to access and modify and redistribute source code isn't the same as having the ability to deploy it to a particular piece of hardware.
Likewise, if I open source a .NET project that doesn't mean it has to include Visual Studio even though VS is the preferred way to build it.