Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.3

VA .NET Programming Standard
VA .NET Programming Standard Standard or Specification

General InformationGeneral Information help

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.

Documentation: Please view the Reference tab.
Description: This VA .NET Programming Standards and Reference Guide has been written to provide VA .NET programmers with a set of coding standards and conventions they can easily follow when developing new .NET applications.

This document reflects solid .NET programming standards and best practices that promote a higher level of maintainability and readability within the software.

In addition, always use proper design and analysis techniques such as:
  • Use proper design and analysis techniques.
  • Participate actively in individual and group code reviews.
  • Build upon test-driven development efforts.
  • Use continuous integration and coordinated implementation practices.
  • Test locally before deployment globally.
  • Use known VA best business practices and VA Lessons Learned.
  • Stay up-to-date on current VA .NET standards.
  • Look for .NET programming standards to evolve and move with it.
The VA benefits in the following manner:
  • Improves the readability, and therefore, maintainability of code.
  • Strongly improves development and technical discussions by offering a common reference point.
  • Reduces the learning curve for new VA developers.
  • Reduces common coding issues/mistakes.
  • Passes on quality .NET programming applications and functionality to the VA Enterprise Network.
The importance and benefits of a consistent coding style are well known. This document draws from some of the industry standards StyleCop coding practices. Unlike guidelines and best practices, the concise set of standards outlined in this document, are meant to be enforced without exception .

Consistency of coding style is more important than using a particular style. When a situation falls out of the scope of this document, experience and informed judgment should be used wherever doubt exists. Request a waiver if it is necessary to deviate from the standards, and propose additions to the standards if you believe you have a best practice that could benefit VA.

Requests for waiver and/or suggestions for changes to this document should be sent to the VA OI&T .NET Standards Committee mailto:VAOITDotNetStandardsCommittee@va.gov.

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:
Decision: Approved. This entry has been approved for general use.
Decision Constraints:
Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v22.7
Decision Date: 07/13/2022 at 20:22:23 UTC
Introduced By: TRM Request
- The information contained on this page is accurate as of the Decision Date (07/13/2022 at 20:22:23 UTC).