Visual Studio 2019 shipped in April 2019 and introduced Live Share for real-time collaborative editing, IntelliCode for AI-assisted completions, a redesigned start window, refreshed installer, and first-class tooling for .NET Core 3.x and .NET 5. It is the last Visual Studio with the 32-bit devenv.exe — Visual Studio 2022 moved to a 64-bit process. Mainstream support ended 13 April 2024; extended support runs to 14 April 2026.
Community (free for individuals, open-source projects, academic use, and small companies up to five developers and US$1M revenue), Professional (commercial use, per-user subscription or perpetual licence), Enterprise (adds IntelliTrace historical debugging, Live Unit Testing, advanced architecture validation, expanded testing tools, MSDN-style benefits via Visual Studio subscriptions).
Three purchase models: standalone perpetual licence (Volume Licensing or Retail), Visual Studio subscription (annual or monthly per user — includes Azure credits, dev/test licences for almost the entire Microsoft stack, Office Pro Plus for the subscriber, Windows VL keys for dev/test), or cloud subscription via CSP. Community is free but the licence terms restrict commercial use in larger organisations — the rule is intentionally narrow and enforced in audits.
Mainstream support ended April 2024; extended support runs to April 2026. After that, no further patches. The successor is Visual Studio 2022 (currently in mainstream) and Visual Studio 2026 (current generation). VS 2019 and VS 2022 can coexist on the same machine — they install side by side under separate installation folders.
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.