title	Release Builds | Microsoft Docs
ms.custom
ms.date	11/04/2016
ms.reviewer
ms.suite
ms.technology	cpp-tools
ms.tgt_pltfrm
ms.topic	article
dev_langs	C++
helpviewer_keywords	debugging [C++], release builds release builds debug builds, converting to release build
ms.assetid	fa9a78fa-f4b5-4722-baf4-aec655c4ff0f
caps.latest.revision	7
author	corob-msft
ms.author	corob
manager	ghogen
translation.priority.ht	cs-cz de-de es-es fr-fr it-it ja-jp ko-kr pl-pl pt-br ru-ru tr-tr zh-cn zh-tw

Release Builds

A release build uses optimizations. When you use optimizations to create a release build, the compiler will not produce symbolic debugging information. The absence of symbolic debugging information, along with the fact that code is not generated for TRACE and ASSERT calls, means that the size of your executable file is reduced and will therefore be faster.

This section presents information on why and when you would want to change from a debug build to a release build. It also discusses some of the problems you may encounter when changing from a debug to a release build:

• Creating a Release Build

• Common Problems When Creating a Release Build

• Fixing Release Build Problems

  • Examining ASSERT Statements

  • Using the Debug Build To Check for Memory Overwrite

  • Debugging a Release Build

  • Checking for Memory Overwrites

See Also

Building C++ Projects in Visual Studio
C/C++ Building Reference