Skip to content

Commit c5f26f2

Browse files
committed
Merged main into live
2 parents 6145a7e + 1543cb1 commit c5f26f2

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

docs/msbuild/how-to-use-environment-variables-in-a-build.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: 'Use Environment Variables in a Build'
33
description: Work with environment variables in MSBuild project files, and use environment variables to set build options without modifying the project file.
4-
ms.date: 8/5/2025
4+
ms.date: 8/11/2025
55
ms.topic: how-to
66
helpviewer_keywords:
77
- environment variables, referencing
@@ -16,6 +16,9 @@ ms.subservice: msbuild
1616

1717
When you build projects, it's often necessary to set build options using information that isn't in the project file or the files that comprise your project. This information is typically stored in environment variables.
1818

19+
> [!NOTE]
20+
> MSBuild treats environment variables as trusted inputs. They can cause MSBuild to load build logic such as tasks, `.targets`, or `.props` files from custom locations or alter how the build executes.
21+
1922
## Reference environment variables
2023

2124
All environment variables that are valid MSBuild property names are available to the MSBuild project file as properties. Valid property names are described in [MSBuild properties](msbuild-properties.md). For example, environment variables that begin with a number aren't available in MSBuild.

0 commit comments

Comments
 (0)