Visual Studio 2019 · licensing decision diagram, not a product screenshot
Assign paid Visual Studio rights to the licensed user. Check Community eligibility and the exact subscription benefits; software provided for development and testing does not automatically carry production-use rights.
Record the exact edition, version, quantity, agreement and support date. Obtain written confirmation of delivery, refund and support terms; a perpetual licence is not a lifetime support guarantee.
On this page
Editions covered
—
Edition matrix with feature differences and the right audience.
In-depth sections
3
Channels, activation, audit, modern management & more.
FAQs answered
4
Common questions buyers and IT admins ask before purchase.
Words of reference
0.2k
Edition and deployment guidance; verify current rights against official sources.
Deep dive
Visual Studio 2019 — what to actually know
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 9 April 2024; extended support (security fixes for version 16.11) runs to 10 April 2029.
01
Editions
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).
02
Licensing and 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.
03
End-of-life and successor
Mainstream support ended April 2024; extended support runs to 10 April 2029 for the final 16.11 release. The successors are Visual Studio 2022 (mainstream support until 12 January 2027) 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.
By channel
Where to buy this product
Confirm that the exact SKU is available in the proposed channel and region. A channel name does not establish entitlement or guarantee a lower price.
Evidence to request
Exact product, edition, version and licence quantity.
Order, invoice and applicable agreement or subscription record.
Ownership in your organisation's account, where applicable.
Written reassignment, renewal and support conditions.
OEM is supplied only pre-installed by hardware manufacturers, never sold as a standalone licence.
Retail / FPPIndividuals & small teams
Boxed or ESD keys, transferable, registered to a Microsoft account.
Monthly / annual seats, managed through partner or admin center.
OEM is not a buying channel for end users. OEM keys are supplied pre-installed by hardware manufacturers and are not sold standalone — choose Retail, Volume or CSP instead.
Support timeline
Lifecycle phases to plan against
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.
Phase 1
Exact product
Identify
Record the release, edition and servicing channel of Visual Studio 2019; family names alone do not establish support dates.
Phase 2
Official lifecycle
Verify
Look up the exact product in Microsoft's lifecycle directory. Fixed and Modern Lifecycle policies differ; not every release has extended support.
Phase 3
Deployment
Plan
Confirm supported operating systems, application dependencies and upgrade rights before deployment.
Phase 4
End of support
Migrate
A perpetual licence can remain valid after support ends, but it does not guarantee security updates. Check any ESU programme separately.
Purchase preparation
What to include in a Visual Studio 2019 quote request
People
Number of developers who will use the licensed software.
IDE
Exact Visual Studio version and edition.
Benefits
IDE-only purchase or subscription benefits required.
Environment
Development/test requirements, separate from production rights.
These are planning inputs, not a licence calculation. Confirm the final quantity and use rights against the exact version and agreement.
Compare like-for-like quotations
Match product, edition, version, quantity and perpetual or subscription terms.
Confirm total cost, renewal conditions and the evidence of ownership supplied.
Obtain written delivery, refund and support conditions before payment.
The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.
DO
Use Community Edition for genuinely independent open-source and individual learning — it is free and feature-equivalent to Professional for small teams.
DON'T
Assume Community is permitted for all organisational work. Enterprise restrictions have specific exceptions for classroom learning, academic research and open-source contributions; read the exact licence terms.
DO
Buy Visual Studio Subscriptions per developer; each seat includes dev/test rights for almost every Microsoft product.
DON'T
Re-use a single subscription across multiple developers — entitlement is per named user.
DO
Burn the included Azure credits — they reset monthly and disappear if unused.
DON'T
Forget GitHub Enterprise is included with VS Enterprise subscriptions in many programmes — check the benefits portal before buying separately.
Typical deployments
How buyers actually use Visual Studio 2019
Illustrative planning scenarios, not customer case studies. Check the exact product rights and deployment requirements.
Scenario 1
Indie / OSS developer
Community Edition + a free GitHub account. Move to a paid subscription only when revenue or team size crosses the licence threshold.
Scenario 2
Enterprise .NET shop
Visual Studio Professional or Enterprise subscriptions per developer, Azure DevOps or GitHub Enterprise for source and pipelines, Azure dev/test subscriptions for non-prod environments.
Scenario 3
Cross-platform / mobile
Visual Studio + .NET MAUI, or VS Code + the relevant extensions. Subscriptions still pay for themselves through Azure credits and the included tooling.
Cost optimisation
Where the savings actually live
Compare entitlement, deployment and renewal costs; savings depend on your workload and written quotation.
💰
Subscriptions > perpetual for most teams
The dev/test rights, Azure credits and bundled GitHub/Office benefits in a VS Subscription pay back the cost long before the IDE itself does.
📊
MSDN / Visual Studio dev-test pricing on Azure
Eligible Visual Studio subscribers may use designated Azure dev/test offers subject to subscription, workload and user requirements. Ordinary Azure VMs do not automatically receive dev/test pricing.
🎯
Right-size Enterprise vs Professional
Compare the exact Visual Studio feature matrix and subscription benefits. IntelliTrace and architectural tooling differ by edition; Live Share is not an Enterprise-only entitlement, and Test Professional is a separate offering.
Counterfeit & risk
Red flags when buying second-hand
These warning signs require further verification; activation alone cannot establish licence ownership.
⚠ 01
Standalone OEM key sold below market
OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is not an eligible standalone purchase; request documented rights through an appropriate channel.
⚠ 02
Lifetime key with no invoice or Microsoft 365 admin center volume licensing record
Request applicable order and agreement records, such as Microsoft Store purchases, CSP subscription records or volume licensing details in the Microsoft 365 admin center. Activation alone is not proof of entitlement.
⚠ 03
Key works once, then 'not genuine' after the next cumulative update
Activation failures can have several causes, including key eligibility, activation counts, connectivity and hardware changes. Check the error through official Microsoft guidance; it does not by itself prove counterfeiting.
⚠ 04
Seller refuses to put the entitlement in your tenant
For tenant-based subscriptions, confirm your organisation controls the tenant and can read its subscription records. Retail and on-premises entitlements use different records; not every licence is assigned through a tenant.
Acronyms
Licensing terms used on this page
Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.
CSP
Cloud Solution Provider — Microsoft's primary indirect channel for subscriptions and cloud services.
Microsoft 365 admin center volume licensing
Volume licensing administration — agreements, keys and downloads are now managed in the Microsoft 365 admin center.
MAK
Multiple Activation Key — a Volume Licensing key with a finite activation count, used for isolated machines.
KMS
Key Management Service — an on-premises activation host that activates clients on a 180-day re-check cycle.
EA
Enterprise Agreement — Microsoft's largest commitment-based volume contract, typically a 3-year term with annual true-ups.
SA
Software Assurance — the upgrade-and-benefits add-on to Volume Licensing; required for new version rights and several mobility scenarios.
Only with security updates. Mainstream support ended 9 April 2024; extended support (security updates only) continues until 10 April 2029. Plan the upgrade before that date — after it, the only path to patches is a paid Extended Security Updates (ESU) programme where Microsoft offers one.
Can VS 2019 still target .NET 8 or .NET 9?+
No — VS 2019 targets up to .NET 5 / .NET Core 3.1 reliably. Building for .NET 6 and later requires Visual Studio 2022 or newer, since the MSBuild SDKs and Roslyn versions needed are not back-ported.
Where can I legitimately buy a license?+
Through Microsoft's Retail channel (where the SKU is still sold), an authorised Cloud Solution Provider (CSP), or a Volume Licensing partner (MPSA, Enterprise Agreement, Open Value, Server & Cloud Enrollment). OEM keys are distributed only pre-installed by hardware manufacturers and stay bound to that device for life — they are not sold to end users as standalone products. For end-of-sale products, second-user (transferred) Volume Licensing through a documented chain of custody is the only legitimate secondary market.
What gets checked in a Microsoft licensing audit?+
Auditors map every installed copy to a proof of purchase (VLSC record, CSP invoice, sealed Retail packaging), verify edition alignment, and confirm CAL counts cover the maximum number of authenticated users or devices during the audit window. Older products are audited the same way as current ones — being out of mainstream support does not waive the licensing obligation.