Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Microsoft Visual Studio

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Microsoft Visual Studio is an integrated development environment (IDE) used to develop console and graphical user interface applications along with Windows Forms applications, ASP.NET applications, web sites, web applications, and web services using native code and managed code. Microsoft Visual Studio supports (to varying degrees) different programming languages, provided a language-specific service exists. Out of the box, the language packs include Visual C++, Visual Basic, and Visual C#. This technology does not contain a database. However, this technology has the capability to import and export data from different types of databases, including Oracle Database and Microsoft Structured Query Language (SQL) Server. Microsoft Visual Studio is available in Community, Express, Professional, Premium, Ultimate, Enterprise, and Test Professional editions. Each of these editions provides the same core functionality. This assessment covers all editions of Microsoft Visual Studio. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: https://dvagov.sharepoint.com/sites/OITMT/SitePages/MTHome.aspx
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.2
Decision Date:	02/05/2024 at 18:07:16 UTC
Introduced By:	ARB
Vendor Name:	Microsoft

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor Desupport Date
6.0	06/01/1998
2008	11/19/2007
2010	04/12/2010
2012	09/12/2012
2013	10/17/2013
2013.1	01/20/2014
2013.2	05/12/2014
2013.3	08/04/2014
2013.4	11/12/2014
2013.5	07/20/2015
2015	07/20/2015
2015.1	11/30/2015
2015.2	03/03/2016
2015.3	06/27/2016	10/01/2025
2017 (15.x)	03/07/2017	04/01/2027
2019 (16.x)	04/02/2019	04/01/2029
2022 (17.x)	11/08/2021

Current Decision Matrix (01/30/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2022

CY2023

CY2024

Future>

Release

6.0

Unapproved

2008

Unapproved

2010

Unapproved

2012

Unapproved

2013

Unapproved

2013.1

Unapproved

2013.2

Unapproved

2013.3

Unapproved

2013.4

Unapproved

2013.5

Unapproved

2015

Unapproved

2015.1

Unapproved

2015.2

Unapproved

2015.3

Divest
[4, 12, 16, 17, 19, 20]

Unapproved

2017 (15.x)

Approved w/Constraints
[4, 12, 16, 17, 19, 20]

Approved w/Constraints
[4, 12, 16, 17, 20, 21]

Approved w/Constraints
[20, 21, 22, 23, 24, 25]

Approved w/Constraints
[20, 23, 24, 25, 26, 27, 28]

Approved w/Constraints
[20, 23, 24, 27, 28, 29, 30, 31, 32]

2019 (16.x)

Approved w/Constraints
[4, 12, 16, 17, 19, 20]

Approved w/Constraints
[4, 12, 16, 17, 20, 21]

Approved w/Constraints
[20, 21, 22, 23, 24, 25]

Approved w/Constraints
[20, 23, 24, 25, 26, 27, 28]

Approved w/Constraints
[20, 23, 24, 27, 28, 29, 30, 31, 32]

2022 (17.x)

Approved w/Constraints
[4, 12, 16, 17, 19, 20]

Approved w/Constraints
[4, 12, 16, 17, 20, 21]

Approved w/Constraints
[20, 21, 22, 23, 24, 25]

Approved w/Constraints
[20, 23, 24, 25, 26, 27, 28]

Approved w/Constraints
[20, 23, 24, 27, 28, 29, 30, 31, 32]

Decision Constraints


[1]	The `Express` editions of Visual Studio are not to be used for national development efforts.

[2]	The `Express` and Test Professional editions of Visual Studio are not to be used for national development efforts.

[3]	The Express and Test Professional editions of Visual Studio are not to be used for national development efforts. This technology has one or more known Common Vulnerability Exposure (CVE) reports, CVE-2014-3802, CVE-2013-3129, CVE-2013-5042 and CVE-2012-1892.

[4]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[5]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[6]	The `Express` and Test Professional editions of Visual Studio are not to be used for national development efforts. This technology has known Common Vulnerability Exposure (CVE) reports applied to other Microsoft products: CVE-2014-3802, CVE-2013-3129, CVE-2013-5042 and CVE-2012-1892. These CVEs have are resolved by applying the following patches: Security Update for Windows 7 (KB2850851) Security Update for Windows Server 2008 (KB2850851) Security Update for Windows Server 2008 R2 x64 Edition (KB2850851) Security Update for Windows Server 2012 (KB2850851)

[7]	The Community, Express and Test Professional editions of Visual Studio are not to be used for national development efforts. This technology has known Common Vulnerability Exposure (CVE) reports applied to other Microsoft products: CVE-2014-3802, CVE-2013-3129, CVE-2013-5042 and CVE-2012-1892. These CVEs are resolved by applying the following patches: Security Update for Windows 7 (KB2850851) Security Update for Windows Server 2008 (KB2850851) Security Update for Windows Server 2008 R2 x64 Edition (KB2850851) Security Update for Windows Server 2012 (KB2850851). If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[8]	The Community, Express and Test Professional editions of Visual Studio must not be used for national development efforts. This technology has known Common Vulnerability Exposure (CVE) reports applied to other Microsoft products: CVE-2014-3802, CVE-2013-3129, CVE-2013-5042 and CVE-2012-1892. These CVEs are resolved by applying the following patches: Security Update for Windows 7 (KB2850851) Security Update for Windows Server 2008 (KB2850851) Security Update for Windows Server 2008 R2 x64 Edition (KB2850851) Security Update for Windows Server 2012 (KB2850851). If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[9]	The Community, Express and Test Professional editions of Visual Studio must not be used for national development efforts. This technology has known Common Vulnerability Exposure (CVE) reports applied to other Microsoft products: CVE-2014-3802, CVE-2013-3129, CVE-2013-5042 and CVE-2012-1892. These CVEs are resolved by applying the following patches: Security Update for Windows 7 (KB2850851) Security Update for Windows Server 2008 (KB2850851) Security Update for Windows Server 2008 R2 x64 Edition (KB2850851) Security Update for Windows Server 2012 (KB2850851). If free trialware is utilized, the software must be purchased or removed at the end of the trial period

[10]	The Community, Express, and Test Professional editions of Visual Studio must not be used for Enterprise Program Management Office (EPMO)-managed projects. This technology has known Common Vulnerability Exposure (CVE) reports applied to other Microsoft products: CVE-2014-3802, CVE-2013-3129, CVE-2013-5042 and CVE-2012-1892. These CVEs are resolved by applying the following patches: Security Update for Windows 7 (KB2850851) Security Update for Windows Server 2008 (KB2850851) Security Update for Windows Server 2008 R2 x64 Edition (KB2850851) Security Update for Windows Server 2012 (KB2850851). If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[11]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[12]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[13]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[14]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[15]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft .NET Framework, Microsoft Internet Explorer (IE), Microsoft Structured Query Language (SQL) Server, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[16]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[17]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[18]	Users must not utilize these technologies Ubuntu, SUSE Linux, Debian Linux, and Fedora Linux, at the time of writing, unapproved in the TRM. Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Firefox, Google Chrome, Microsoft .NET Framework, Microsoft Internet Explorer (IE), Microsoft Structured Query Language (SQL) Server, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Microsoft Software License Terms - Microsoft Visual Studio Community 2019 statement that is attached in the reference section of this entry. Users are not allowed to use this software outside of these guidelines. If you are an enterprise, your employees and contractors may not use the software to develop or test your applications, except for: (i) open source; (ii) Visual Studio extensions; (iii) device drivers for the Windows operating system; (iv) SQL Server development.

[19]	Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Firefox, Google Chrome, Microsoft .NET Framework, Microsoft Internet Explorer (IE), Microsoft Structured Query Language (SQL) Server, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Microsoft Software License Terms - Microsoft Visual Studio Community 2019 statement that is attached in the reference section of this entry. Users are not allowed to use this software outside of these guidelines. If you are an enterprise, your employees and contractors may not use the software to develop or test your applications, except for: (i) open source; (ii) Visual Studio extensions; (iii) device drivers for the Windows operating system; (iv) SQL Server development.

[20]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[21]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Microsoft Software License Terms - Microsoft Visual Studio Community 2019 statement that is attached in the reference section of this entry. Users are not allowed to use this software outside of these guidelines. If you are an enterprise, your employees and contractors may not use the software to develop or test your applications, except for: open source Visual Studio extensions device drivers for the Windows operating system SQL Server development

[22]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[23]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[24]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[25]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[26]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Google Chrome, Firefox, Microsoft Edge, Microsoft Structured Query Language (SQL) Server and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Microsoft Software License Terms - Microsoft Visual Studio Community 2019 statement that is attached in the reference section of this entry. Users are not allowed to use this software outside of these guidelines. If you are an enterprise, your employees and contractors may not use the software to develop or test your applications, except for: open source Visual Studio extensions device drivers for the Windows operating system SQL Server development

[27]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

[28]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[29]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users should not use Firebird with this technology, as it is unapproved at this time. Other options are available, see Category Tab for details. Users must ensure that Google Chrome, Firefox, Microsoft Edge, PostgreSQL, Microsoft Structured Query Language (SQL) Server, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Microsoft Software License Terms - Microsoft Visual Studio Community 2019 statement that is attached in the reference section of this entry. Users are not allowed to use this software outside of these guidelines. If you are an enterprise, your employees and contractors may not use the software to develop or test your applications, except for: open source Visual Studio extensions device drivers for the Windows operating system SQL Server development

[30]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

[31]	If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details.

[32]	This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details.

Note:

At the time of writing, version 17.8 is the most current version, released 11/14/2023.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Active Server Pages (ASP).NET and web development	Active Server Pages (ASP).NET, also known as Visual Studio .NET Developer, is used to create web sites, web applications and web services using Active Server Pages ASP.NET through either the C# or VB.NET languages. ASP.NET and web development can use the Visual Studio Web Designer to graphically design web page layouts.
Application Insights Tools for Visual Studio	This optional add-on is downloaded via the Visual Studio 2015 menu. This module offers improvements over functionality that shipped with Visual Studio 2015 Update 1. Noteworthy additions include the ability to search Application Insights telemetry emitted in the local debug session and better targeted Application Insights toasts in Visual Studio.
Application Verifier	Application Verifier is an optional module that is a runtime verification feature for native code that assists in finding subtle programming errors that can be difficult to identify with normal application testing. This module is used with older versions of Visual Studio.
Azure development	Azure Software Development Kits (SDKs), tools, and project for developing cloud apps and creating resources using .NET Core and .NET.
Debugging Tools for Windows	This component is an optional component that supports debugging functionality.
Extensible Application Markup Language (XAML) Designer	XAML Designer in Visual Studio provides a visual interface to help you design XAML-based apps.
Microsoft Build Tools 14.0 (amd64)	Microsoft Build Tools 14.0 (amd64) provides the essential tools for building managed applications.
Microsoft Help Viewer	Microsoft Help Viewer (HV) is the offline help system (local help) developed by Microsoft that ships with Visual Studio 2010.
Microsoft Macro Assembler	The Microsoft Macro Assembler (MASM) is an x86 assembler that uses the Intel syntax for writing low-level Microsoft Windows object code. MASM is a feature that consumes x86 assembly language programs and generates corresponding binaries. Assembly language programs built with MASM can be edited and debugged using C++. MASM contains a macro language that has features such as looping, arithmetic, and text string processing.
Roslyn Language Services	.NET Compiler Platform, also known by its nickname Roslyn Language Services, is a set of open-source compilers and code analysis application program interfaces (APIs) for C# and Visual Basic .NET languages from Microsoft.
SQL Server Analysis Services (SSAS)	Analysis Services is an analytical data engine (VertiPaq) used in decision support and business analytics. It provides enterprise-grade semantic data models for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
SQL Server Data tool (SSDT)	SQL Server Data Tools (SSDT) is a modern development tool for building SQL Server relational databases, databases in Azure SQL, Analysis Services (AS) data models, Integration Services (IS) packages, and Reporting Services (RS) reports. With SSDT, you can design and deploy any SQL Server content type with the same ease as you would develop an application in Visual Studio.
SQL Server Integration Services (SSIS)	SQL Server Integration Services is a platform for building enterprise-level data integration and data transformations solutions. Use Integration Services to solve complex business problems by copying or downloading files, loading data warehouses, cleansing and mining data, and managing SQL Server objects and data.
SQL Server Reporting Services (SSRS)	SQL Server Reporting Services (SSRS) provides a set of on-premises tools and services that create, deploy, and manage mobile and paginated reports.
Visual Basic	Visual Basic is Microsoft`s implementation of the Visual Basic.NET (VB.NET) language, associated features, and language services. Visual Basic is to be used for Rapid Application Development of console and Graphical User Interface (GUI) applications. Visual Basic supports the Visual Studio Class designer, Forms designer, and Data designer.
Visual C#	Visual C#, Microsoft`s implementation of the C# language, targets the .NET Framework. Visual C# supports the Visual Studio Class designer, Forms designer, and Data designer. Visual C# is used to develop both desktop and web applications.
Visual C++	Visual C++ is Microsoft`s implementation of a compiler for either C or C++ languages. this component also supports the C++ Common Language Infrastructure (C++/CLI) specification to write managed code (managed by .NET), and mixed-mode code (a mix of native and managed code).
Visual Studio 2010 Tools for Office Runtime	Visual Studio 2010 Tools for Office Runtime is a set of development tools used to develop Microsoft Office extensions in a variety of different languages, not just Visual Basic or Visual C++.
Visual Studio Services Hub	The Visual Studio Services Hub is a support portal that provides visibility into all of your Microsoft products and services, tailored training and support resources, and solution monitoring to efficiently help prevent and resolve issues.
Visual Studio Team Foundation Server Power Tools	Visual Studio Team Foundation Server Power Tools are a set of enhancements and command-line utilities that increase productivity of Team Foundation Server scenarios.
Xamarin	Xamarin is a cross-platform framework for building applications.


Application Technology Development Tools	Integrated Development Environment (IDE)

- The information contained on this page is accurate as of the Decision Date (02/05/2024 at 18:07:16 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (01/30/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (01/30/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES