Merge pull request #10738 from MicrosoftDocs/main638817448507139435sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/deployment/index.yml

@@ -11,7 +11,7 @@ metadata:
   author: ghogen
   ms.author: ghogen
   manager: mijacobs
-  ms.date: 5/20/2024
+  ms.date: 5/1/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 

docs/ide/how-to-sign-application-and-deployment-manifests.md

@@ -13,8 +13,8 @@ helpviewer_keywords:
 - ClickOnce deployment [Visual Studio], signing assemblies
 - key files [Visual Studio]
 - assemblies [Visual Studio], signing
-author: ghogen
-ms.author: ghogen
+author: mikejo5000
+ms.author: mikejo
 manager: mijacobs
 ---
 # Sign application and deployment manifests

docs/ide/managing-assembly-and-manifest-signing.md

@@ -9,8 +9,8 @@ helpviewer_keywords:
 - signing manifests [Visual Studio]
 - application manifests [Visual Studio]
 - assemblies [Visual Studio], signing
-author: ghogen
-ms.author: ghogen
+author: mikejo5000
+ms.author: mikejo
 manager: mijacobs
 ---
 # Manage assembly and manifest signing

docs/ide/using-regular-expressions-in-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: Use regular expressions and review examples
 description: Explore some regular expression characters, operators, constructs, and pattern examples that you can use in Visual Studio.
-ms.date: 01/11/2024
+ms.date: 5/1/2025
 ms.topic: conceptual
 f1_keywords:
 - vsregularexpressionhelp
@@ -98,7 +98,7 @@ For more information about named capture groups, see [Named matched subexpressio
 | Pattern | Description |
 | - | - |
 | `int ([_A-Za-z][_A-Za-z0-9]*)` | Match single integer definitions. Identifiers begin with one uppercase or lowercase letter, followed by zero or more (indicated by `*`) letters or numbers. The identifier is captured as `$1` by the outer parentheses. |
-| `(private|internal|public)*\s*([\w]+\s+)int\s+([_A-Za-z][_A-Za-z0-9]*)\s+=\s+[+-]+(\d)+` | Match C# integer declarations that are initialized to integer literals, capturing the various parts, including the access level, modifiers like `const` or `static`, the identifier, and the defined value. Note the use of `\s+` for at least one whitespace character, or `\s*` if whitespace might or might not occur. |
+| `(private\|internal\|public)*\s*([\w]+\s+)int\s+([_A-Za-z][_A-Za-z0-9]*)\s+=\s+[+-]+(\d)+` | Match C# integer declarations that are initialized to integer literals, capturing the various parts, including the access level, modifiers like `const` or `static`, the identifier, and the defined value. Note the use of `\s+` for at least one whitespace character, or `\s*` if whitespace might or might not occur. |
 | `foreach\s*\(([\w\d]*)\s+([\w\d]*)\s+in\s+(.*)\)` | Match the opening line of a `foreach` loop. The literal parentheses  are escaped with backslash (`\`). The various groups are captured as `$1`, `$2`, and `$3` by the unescaped parentheses. |
 | `#define\s+([_A-Za-z][_A-Za-z0-9]*)` | Matches `#define` definitions (without the value, if any). The defined token is stored in `$1`. |
 | `#include\s+["<](.*)[">]` | Match includes in a C++ source file. |

docs/msbuild/evaluate-items-and-properties.md

@@ -36,6 +36,8 @@ If you don't specify a target on the command line by using the `-target` option,
 
 If you specify `-getTargetResult`, any targets requested are automatically built, as if you specified them with `-target`, along with any other targets you requested.
 
+Be aware that properties are evaluated before items, so if you're using `-getProperty` for a property that references an item, you get a different output depending on whether or not you're getting the result before or after item evaluation occurs.  For example, if you use `-getProperty` without using the `-target` option (or `-getTargetResult`), then you get the property value without item evaluation, but if you do specify `-targets` (or `-getTargetResult`), then you get the final result after item evaluation. See [How MSBuild builds projects](build-process-overview.md).
+
 You can use these commands with `MSBuild.exe` or with `dotnet build`, or other `dotnet` commands such as `dotnet publish`. See [MSBuild command-line reference](msbuild-command-line-reference.md) and [dotnet command](/dotnet/core/tools/dotnet).
 
 If you use `-getProperty` to request a single property, the output is emitted as a string of text. That means you can easily consume the value in scripting scenarios, or within a more complex command line.

docs/msbuild/how-to-exclude-files-from-the-build.md

@@ -1,7 +1,7 @@
 ---
 title: Exclude Files from the Build
 description: Discover how to explicitly exclude or conditionally include files from builds for MSBuild project files with attributes and wildcards.
-ms.date: 05/15/2024
+ms.date: 05/1/2025
 ms.topic: how-to
 helpviewer_keywords:
 - MSBuild, wildcards
@@ -76,7 +76,7 @@ If you're using wildcards to include all the files in one directory or a nested
 
 `Exclude` is not actually an item operation; it can't be used by itself, but only as a modifier for `Include`.
 
-### To include all `.cs` or `*.vb` files except `Form2`
+### To include all `.cs` or `.vb` files except `Form2`
 
 - Use one of the following `Include` and `Exclude` attributes:
 

docs/msbuild/how-to-extend-the-visual-studio-build-process.md

@@ -1,7 +1,7 @@
 ---
 title: Extend and customize the build process
 description: Explore several ways you can modify the build process so you can control and customize how your projects build, including overriding properties.
-ms.date: 05/16/2024
+ms.date: 5/1/2025
 ms.topic: how-to
 helpviewer_keywords:
 - MSBuild, overriding predefined targets

docs/msbuild/target-build-order.md

@@ -1,7 +1,7 @@
 ---
 title: Set the run order for MSBuild targets
 description: Specify the order in which MSBuild targets run and whether the input to one target depends on the output of another target.
-ms.date: 05/15/2024
+ms.date: 5/1/2025
 ms.topic: how-to
 helpviewer_keywords:
 - msbuild, build order