Share via

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.

In this section

Common Problems When Creating a Release Build
Fixing Release Build Problems
Using VERIFY Instead of ASSERT
Using the Debug Build to Check for Memory Overwrite
How to: Debug a Release Build
Checking for Memory Overwrites
Optimizing Your Code

See also

C/C++ Building Reference