Skip to content

Commit c33179a

Browse files
Merge pull request #14184 from ghogen/build-configuration-ui-update
Add details on predefined constants
2 parents 401cccf + e4bf176 commit c33179a

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed
36.1 KB
Loading

docs/ide/understanding-build-configurations.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Understand build configurations
33
description: Discover how to work with build configurations when you need to build your projects with different settings in Visual Studio.
4-
ms.date: 11/14/2024
4+
ms.date: 8/7/2025
55
ms.subservice: compile-build
66
ms.topic: conceptual
77
f1_keywords:
@@ -67,9 +67,11 @@ The configuration and platform that a project targets are used together to speci
6767
![Screenshot of project designer configurations.](media/understanding-build-configurations/project-designer-configuration.png)
6868
:::moniker-end
6969
:::moniker range=">=vs-2022"
70-
![Screenshot of project designer configurations.](media/vs-2022/build-configuration-project-designer-configuration.png)
70+
![Screenshot of project designer configurations.](media/vs-2022/understanding-build-configurations/project-designer-build-configurations.png)
7171
:::moniker-end
7272

73+
The predefined constants for each configuration are shown underneath the textbox where you can enter your own. These predefined constants are defined by the SDK your project uses. To see where these properties are defined, you can look for how the MSBuild property `DefineConstants` is defined and modified in the .NET SDK installation folder where `.props` and `.targets` files are located. The SDKs provide MSBuild properties that you can set in the project file to disable the predefined definitions; for example, see [DisableImplicitFrameworkDefines](/dotnet/core/project-sdk/msbuild-props#disableimplicitframeworkdefines).
74+
7375
## How Visual Studio associates project configurations with solution configurations
7476

7577
When you define a new solution configuration and don't copy settings from an existing one, Visual Studio uses the following criteria to associate the existing project configurations with the new solution configuration. The criteria are evaluated in the order shown.

0 commit comments

Comments
 (0)