A mature commercial IDE with a long support horizon
Microsoft Visual Studio 2022 Professional Edition
Build, debug, test and maintain professional applications in Microsoft’s established 64-bit Windows IDE, supported on its final 17.14 servicing baseline through January 2032.
Visual Studio 2022 Professional is the deliberate middle ground for paid development: more appropriate than relying on Community eligibility, yet more economical than Enterprise when advanced architecture governance, IntelliTrace, Live Unit Testing and built-in Code Coverage are not required. It is especially persuasive for solutions, extensions and build pipelines already validated on the 17.x generation.
The decision in one minute
Choose 2022 when continuity has measurable value
Visual Studio 2022 Professional remains relevant because support longevity and platform familiarity can matter more than chasing the newest IDE generation. Choose it when the work is commercial, the team needs a complete development environment, and your repositories, extensions, toolchains or governance processes are already qualified on Visual Studio 2022.
Scale beyond 32-bit limits
Visual Studio 2022 was the first 64-bit Visual Studio IDE, allowing the development environment to use more memory when loading large solutions and tooling.
Write with context
Navigate, complete, refactor and inspect code in an editor built to understand projects, symbols and relationships—not merely colourise text.
Debug precisely
Set breakpoints, inspect state, step through execution and use integrated diagnostics to move from a symptom to defensible evidence.
Shorten the feedback loop
Apply supported .NET or C++ changes while an application is running, reducing unnecessary stop-edit-rebuild cycles.
A tighter daily loop
Stay inside the flow from idea to reviewed change
Visual Studio combines solution-aware editing with build, Hot Reload, testing, debugging, source control and deployment workflows. The advantage is continuity: less time assembling context across separate tools and more time making a change, proving it, reviewing it and preparing it for release.
Current 17.14 servicing releases continue to update Git, extension and eligible GitHub Copilot integrations. Copilot can provide conversational assistance and agent-oriented workflows, while the developer remains responsible for reviewing changes, commands, test results and security implications.
Copilot is a separate entitlement
GitHub Copilot features require an eligible Copilot plan, sign-in and connectivity. Purchasing Visual Studio 2022 Professional does not automatically include every Copilot plan, cloud service, preview or agent capability.
A complete professional workbench
Tools that serve the work you do every day
Professional concentrates on the broad, high-frequency capabilities that help a developer or compact team produce and maintain real software reliably.
Test Explorer
Discover, run, group and diagnose supported unit tests. In Visual Studio 2022, Professional includes everyday unit-testing workflows, but not Enterprise-only Live Unit Testing, IntelliTest, Microsoft Fakes or built-in Code Coverage.
Git and pull requests
Clone, branch, commit, merge, resolve conflicts and review supported pull requests with project context close at hand.
CodeLens context
Keep references, changes, authors and supported source-control insight close to the code instead of reconstructing history manually.
Performance evidence
Use the Performance and Diagnostics Hub and supported profiling tools to investigate CPU, memory and runtime behaviour.
Cloud and containers
Build web applications, APIs, services and containerised solutions with workload-based tooling for .NET, Azure, Docker and connected platforms.
Many destinations
Use one Windows IDE for supported desktop, web, cloud, mobile, game, data, Python, Node.js and C++ cross-platform workloads.
Edition comparison
Visual Studio 2022 Professional vs Enterprise vs Community
The right edition is a business decision, not a feature-count contest. Professional is compelling when commercial eligibility, a complete IDE and disciplined daily workflows matter more than Enterprise-only architecture and test intelligence.
| Decision factor | Professional | Enterprise | Community |
|---|---|---|---|
| Best fit | Independent professionals and small commercial teams | Large, complex, quality-critical or highly governed software engineering | Individuals, learning, open source and other eligible scenarios |
| Commercial use | Commercial use under the purchased licence terms | Commercial and enterprise use under the purchased terms | Usage is restricted by Community licence eligibility; verify before relying on it |
| Editor, IntelliSense, refactoring and Peek | Included | Included | Included, subject to licence terms |
| CodeLens source-control indicators | Included for supported Git or Azure DevOps workflows | Included | CodeLens is present, but source-control indicators are not included |
| Debugger, Test Explorer, Git and core diagnostics | Included | Included | Included, subject to licence terms |
| Live Unit Testing | Not included | Enterprise capability | Not included |
| Code Coverage, IntelliTest and Microsoft Fakes | Not included | Enterprise capabilities where supported | Not included |
| Create and edit Code Maps or dependency graphs | Can open supported diagrams created in Enterprise as read-only | Create and edit | Can open supported diagrams created in Enterprise as read-only |
| Live Dependency Validation and architecture validation | Not included | Enterprise capability | Not included |
| IntelliTrace and Code Map debugger integration | Not included | Enterprise capability | Not included |
| Performance and Diagnostics Hub | Core diagnostics included | Included with added Enterprise-specific depth | Core diagnostics included, subject to licence terms |
| Supported 17.14 baseline | Current Channel 17.14 through January 2032 when kept serviced | Same supported baseline | Latest Current Channel servicing release required |
| Purchase logic | Choose for a capable paid-development environment without the Enterprise premium | Choose when defect cost, architecture risk and diagnosis time justify deeper tooling | Choose only when the intended use satisfies current Community terms |
Feature availability can vary by workload, language, project type, Visual Studio update and associated service entitlement. Check current Microsoft comparison and licensing terms for the intended deployment.
One workspace, many outcomes
Build for desktop, web, cloud and beyond
Visual Studio uses workload-based installation so each developer can install the toolchains that suit the job. Supported scenarios include Windows desktop, ASP.NET and web development, Azure, Docker, .NET, C++, Python, Node.js, Office and business applications.
Visual Studio 2022 version 17.12 or later supports targeting .NET 9, while 17.8 or later supports .NET 8. It does not provide integrated .NET 10 targeting; Microsoft maps .NET 10 to Visual Studio 2026 version 18.0 or later. C++ teams can use modern MSVC tooling and cross-platform workflows, and existing solutions can often be modernised in stages with multi-targeting where supported.
- .NET and C#: desktop, web, API, cloud and service workloads.
- C++: Windows, native performance and supported cross-platform development.
- Web and scripting: JavaScript, TypeScript, Python and Node.js tooling where installed.
- Delivery: local publishing, supported Azure destinations, containers and CI/CD-connected workflows.
Generation decision
Visual Studio 2022 Professional vs Visual Studio 2026 Professional
Newer is not automatically better for every repository. The correct generation depends on target frameworks, extension compatibility, operating controls and how much change the organisation is ready to absorb.
| Decision area | Visual Studio 2022 Professional | Visual Studio 2026 Professional |
|---|---|---|
| Best reason to choose | Existing projects, extensions and build systems already validated on the mature 17.x generation | New development needing Microsoft’s latest IDE generation and newest platform integration |
| .NET target ceiling in the full IDE | .NET 9 with Visual Studio 17.12 or later | .NET 10 with Visual Studio 18.0 or later |
| Support model | Fixed Lifecycle: mainstream support to January 2027 and extended support to January 2032 | Modern Lifecycle: two-year annual product cycle, subject to Microsoft servicing policy |
| Servicing baseline | Version 17.14 Current Channel, kept on its latest servicing update | Current supported Visual Studio 2026 servicing channel |
| Change profile | Lower migration pressure for repositories already qualified on 17.x | Greater access to new platform and AI-assisted workflows, with more validation work for extensions and processes |
| Side-by-side planning | Different major Visual Studio versions can generally coexist, but shared SDKs, extensions, toolchains and file associations still require a controlled pilot. | |
The practical rule
Choose 2022 when the application lifecycle and validated toolchain are anchored to .NET 9 or earlier. Choose 2026 when .NET 10 or the newest IDE-generation capabilities are explicit project requirements.
A day in the life
From client request to release candidate
Imagine a two-developer consultancy maintaining a customer portal and companion Windows utility. Professional keeps the high-value path coherent without forcing the team into an enterprise-scale tool purchase.
Understand
Open the solution, use CodeLens, search and navigation to trace the relevant service, UI and test code.
Change
Refactor with symbol awareness, use supported completion and optionally consult separately licensed Copilot assistance.
Prove
Build the affected projects, run targeted tests in Test Explorer, debug edge cases and profile suspected hotspots.
Review and ship
Commit on a branch, open or review the pull request and publish through the team’s chosen deployment workflow.
Practical adoption
Modernise without turning every upgrade into a rewrite
Visual Studio 2022 can open supported C++ projects created as far back as Visual Studio 2010, with choices to upgrade or retain compatible earlier toolsets. Across project types, the safest approach is deliberate: inventory projects, extensions and build dependencies; test a representative branch; modernise the highest-value layer; and preserve a rollback path.
Stage the upgrade
Validate solutions, target frameworks, package dependencies, extensions and CI agents before rolling the IDE across the team.
Digital fulfilment
Receive the purchase information digitally and follow the supplied activation instructions. Delivery time and activation method depend on the exact offer.
Human assistance
Software Mart Australia advertises remote support to help with delivery and activation questions related to the order.
System requirements
Plan the workstation before deployment
Visual Studio is a substantial development environment. Microsoft’s baseline is useful for installation; a professional workstation should be planned for the actual solution size, workloads, containers, emulators and parallel builds.
| Area | Microsoft baseline or support position | Practical buying guidance |
|---|---|---|
| Operating system | Supported 64-bit editions of Windows 11, or Windows Server 2025, 2022, 2019 or 2016 in the listed Standard/Datacenter editions | Microsoft’s current requirements no longer list Windows 10 for the full Visual Studio 2022 IDE. Confirm the exact Windows edition and servicing state. |
| Processor | x64 or ARM64; quad-core or better recommended | More cores help large builds, analysis, local services and parallel test execution. |
| Memory | 4 GB minimum | Microsoft recommends 16 GB for typical professional solutions. Containers, emulators and large repositories may justify more. |
| Storage | About 850 MB–210 GB depending on selected features; typical installs 20–50 GB | Use an SSD and preserve capacity for SDKs, package caches, repositories, containers and build outputs. |
| Display | 1366×768 minimum; 1920×1080 recommended | A high-resolution or multi-monitor setup materially improves debugging, diagnostics and review work. |
| Installation dependencies | Administrator rights for install/update, .NET Framework 4.8 runtime and WebView2 | Coordinate endpoint policies, proxy access, update channels and component caching before team rollout. |
Arm64 and virtual-environment caution
Arm64 support has workload limitations, including exclusions in Azure development except container tools, parts of data workloads, data science, Python, mobile C++ and Office/SharePoint development. Microsoft also lists unsupported environments such as 32-bit systems, Windows in S mode, the full IDE in Windows containers, nonpersistent virtual machines and pooled multiuser VDI arrangements. Validate the exact workload against Microsoft’s current requirements before purchase.
Servicing and lifecycle
A fixed lifecycle through January 2032
Visual Studio 2022 follows Microsoft’s ten-year Fixed Lifecycle. It started on 8 November 2021, mainstream support ends on 12 January 2027, and extended support ends on 13 January 2032. Extended support focuses on security updates rather than new platform features.
Version 17.14 is the final Current Channel baseline and is supported through January 2032 when installations remain on the latest 17.14 servicing release. There is no separate 17.14 LTSC channel. Earlier 17.12 LTSC support ended on 14 July 2026, so organisations still on that branch should plan a supported move.
Deployment checklist
- Inventory required workloads, SDKs, extensions and build tools.
- Standardise on the latest supported 17.14 servicing release.
- Test representative repositories and CI agents before rollout.
- Document Copilot, cloud-service and package-feed access separately.
- Keep installers, purchase records and entitlement evidence organised.
Buy with the right expectation
Confirm the licence, not just the product name
Visual Studio Professional can be sold through different Microsoft licensing channels and offers. The words “Professional” and “genuine” do not by themselves define whether an offer is perpetual, subscription-based, transferable, device- or user-assigned, or supplied with Microsoft subscriber benefits.
Before placing an order, ask Software Mart Australia to confirm in writing
- The exact Microsoft licence programme, product identifier and edition supplied.
- Whether the right is perpetual or time-limited, and whether future versions are included.
- Whether the licence is assigned per user or per device and any transfer/reassignment conditions.
- The activation method, region restrictions, business-use rights and proof-of-licence documentation.
- Whether Visual Studio subscription benefits, Azure DevOps, Azure credit, training, support incidents or GitHub Copilot are included. Do not assume they are.
This page explains the software edition and current Microsoft platform documentation; the seller must define the legal rights and benefits attached to this particular SKU.
Frequently asked questions
Visual Studio 2022 Professional: 24 practical answers
1. Who is Visual Studio 2022 Professional for?
It is a strong fit for independent developers, consultants and small commercial teams that need a complete Windows IDE without Enterprise-only architecture, test-intelligence and historical-debugging features.
2. Can I use Professional for commercial development?
Yes, under the rights of the licence actually supplied. Confirm the licence programme, assignment model and business-use terms with the seller.
3. How is Professional different from Community?
The core IDE overlaps substantially, but Community use is restricted by Microsoft eligibility terms. Professional is the paid edition intended to remove that eligibility question for properly licensed commercial users.
4. When should I choose Enterprise instead?
Choose Enterprise when Live Unit Testing, Code Coverage, IntelliTest, Microsoft Fakes, editable Code Maps, dependency validation, IntelliTrace or related advanced engineering capabilities justify the additional cost.
5. Does Professional include CodeLens?
Yes. Microsoft’s edition comparison lists CodeLens among the shared productivity features.
6. Does Professional include Live Unit Testing?
No. Live Unit Testing is an Enterprise differentiator in Microsoft’s edition comparison.
7. Does Professional include Code Coverage?
No. Microsoft lists Code Coverage with the Enterprise testing capabilities, not Professional.
8. Can Professional run unit tests?
Yes. Professional includes standard unit-testing and Test Explorer workflows for supported test frameworks; these are distinct from Enterprise-only Live Unit Testing and coverage tools.
9. Is GitHub Copilot included?
Do not assume so. Copilot requires an eligible plan, account, sign-in and connectivity; entitlement is separate from the Visual Studio edition unless the specific offer states otherwise.
10. What AI features are available?
With the appropriate Copilot entitlement, current Visual Studio 2022 releases support chat, code assistance, planning and agent-oriented workflows. Availability can vary by plan, update, account and preview status.
11. What is the newest .NET target supported by Visual Studio 2022?
Visual Studio 2022 version 17.12 or later supports targeting .NET 9. Microsoft requires Visual Studio 2026 version 18.0 or later for integrated .NET 10 development.
12. Can I build C++ applications?
Yes. Install the relevant C++ workloads for Windows, native and supported cross-platform development.
13. Does it support Python and Node.js?
Yes, through the relevant workloads and components. Project-specific package managers, runtimes and extensions may also be required.
14. Can I build for Azure and Docker?
Yes, supported Azure, web and container development workflows are available when the required workloads and external services are installed and licensed.
15. Does Visual Studio 2022 run on Windows 10?
The full Visual Studio 2022 IDE requirements list supported Windows 11 and Windows Server editions, not Windows 10. Plan an operating-system upgrade before deployment.
16. Does it run on Arm64 Windows?
Yes on supported Windows 11 Arm64 systems, but several workloads and components have limitations. Check the current Microsoft Arm64 list against the planned toolchain.
17. How much RAM should I choose?
Microsoft lists 4 GB minimum and recommends 16 GB for typical professional solutions. Large repositories, containers, emulators and parallel builds can justify more.
18. How much disk space is required?
Installation can range from roughly 850 MB to 210 GB; Microsoft describes 20–50 GB as typical. Keep additional SSD capacity for SDKs, repositories, packages and build outputs.
19. Can Visual Studio 2022 sit beside Visual Studio 2026?
Different major Visual Studio versions can generally coexist, but shared SDKs, file associations, extensions and toolchains still require a controlled pilot and repository-level testing.
20. What is the support lifecycle?
Visual Studio 2022 follows a Fixed Lifecycle: mainstream support ends 12 January 2027 and extended support ends 13 January 2032. Use the latest serviced 17.14 release to remain supported.
21. Is a Professional subscription included?
Not necessarily. Microsoft sells Visual Studio Professional subscriptions with benefits, but that does not prove this retailer SKU includes a subscription. Confirm the exact offer.
22. Is the licence perpetual?
The edition name alone does not answer that. Ask the seller to state whether the supplied right is perpetual or subscription-based and how reassignment, transfer and upgrades work.
23. How is the product delivered?
The listing describes digital delivery. Exact timing, download source, activation method and documentation should be confirmed with Software Mart Australia before ordering.
24. What should I retain after purchase?
Keep the invoice, licence terms, product identifier, activation instructions, seller correspondence and any Microsoft entitlement or account records together for audit and recovery.
Professional tools. Focused investment.
Give commercial developers the IDE their work deserves
Choose Visual Studio 2022 Professional for solution-aware productivity, integrated debugging, testing, Git collaboration and broad application delivery—without paying for Enterprise capabilities the team does not need.
Confirm the exact licence programme, activation method, inclusions and system compatibility before purchase.
