Visual Studio 2017 shipped in March 2017 and was the first release with the modern, workload-based installer — instead of a single 30+ GB installer, developers picked the workloads they needed (.NET desktop, ASP.NET, mobile with Xamarin, C++ desktop, Linux C++, game development with Unity, Azure, etc.). It introduced live unit testing, lightweight solution load, Open Folder support for non-MSBuild codebases, and first-party tooling for .NET Core 1.x and 2.x. Mainstream support ended 12 April 2022; extended support ended 9 April 2027 (varies by edition).
Community (free, same eligibility rules as later versions), Professional (commercial use), Enterprise (advanced testing, architecture and debugging tools). All editions share the same workload-based installer and can target the same frameworks — the difference is in productivity tooling, not in what you can ship.
Mainstream support ended April 2022. Extended support runs to 9 April 2027 for both Professional and Enterprise. After that, no further patches. Migration path is straightforward: open a 2017 .sln file in VS 2019 / 2022 / 2026 and the IDE prompts to upgrade — project files are compatible going forward, with toolset retargeting handled automatically for most workloads.
Relative fit of each licensing channel for typical buyers of this product. Calibrate against your own scale and renewal strategy.
Visual Studio is licensed per developer (subscription), and the included Azure credits, dev/test rights and software downloads are usually worth more than the IDE itself. Treat it as a developer benefit package, not a single product.
The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.
Three reference deployments — find the closest match and adapt rather than starting from zero.
None of these are tricks — they are the same levers Microsoft's own licensing specialists pull on every renewal.
These four signals show up in every counterfeit-licence case we have seen. If any of them is present, walk away — no discount makes it worthwhile.
OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is almost certainly leaked, harvested from scrapped hardware, or fully counterfeit.
Microsoft entitlement always leaves a paper trail — a Volume Licensing Service Center record, a CSP invoice, a sealed Retail box with a COA, or a Microsoft Store order. No proof = no defence in an audit.
Classic symptom of a MAK key that has exceeded its activation pool, or a KMS key being abused outside its volume programme. Microsoft revokes these centrally; the activation grace period is short.
Legitimate CSPs and LARs transfer the licence into your Microsoft 365 / Azure / VLSC tenant under your domain. If the seller insists on activating 'for you' on their account, you do not own anything.
Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.