Yes. When clients specify Visual Studio 2017, they usually require that exact IDE version to ensure compatibility with their build process, dependencies, and tooling. Using a newer version can sometimes introduce errors they want to avoid.
In many cases, yes. Developers often revert to Visual Studio 2017 because newer IDEs may change compilers, project formats, or default settings that affect older solutions.
For many teams, yes. That’s why Visual Studio 2017 is still widely used for maintenance work, as it matches the environment the software was originally built in.
Most developers and even many companies use the Professional edition. Enterprise is typically chosen only when advanced testing, diagnostics, or large-team governance tools are required.
Yes. Reproducing identical builds often requires using the same Visual Studio version originally used, which is why teams purchase Visual Studio 2017 specifically.