You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/core/project-sdk/msbuild-props.md
+34-1Lines changed: 34 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -914,8 +914,9 @@ To remove this warning and continue to use the version of code analyzers in the
914
914
915
915
## Runtime configuration properties
916
916
917
-
You can configure some run-time behaviors by specifying MSBuild properties in the project file of the app. For information about other ways of configuring run-time behavior, see [Runtime configuration settings](../runtime-config/index.md).
917
+
You can configure some runtime behaviors by specifying MSBuild properties in the project file of the app. For information about other ways of configuring runtime behavior, see [Runtime configuration settings](../runtime-config/index.md).
The `AutoreleasePoolSupport` property configures whether each managed thread receives an implicit [NSAutoreleasePool](https://developer.apple.com/documentation/foundation/nsautoreleasepool) when running on a supported macOS platform. For more information, see [`AutoreleasePool` for managed threads](../runtime-config/threading.md#autoreleasepool-for-managed-threads).
@@ -1029,6 +1042,26 @@ The `TieredCompilationQuickJitForLoops` property configures whether the JIT comp
1029
1042
</PropertyGroup>
1030
1043
```
1031
1044
1045
+
### TieredPGO
1046
+
1047
+
The `TieredPGO` property controls whether dynamic or tiered profile-guided optimization (PGO) is enabled. Set the value to `true` to enable tiered PGO. For more information, see [Profile-guided optimization](../runtime-config/compilation.md#profile-guided-optimization).
1048
+
1049
+
```xml
1050
+
<PropertyGroup>
1051
+
<TieredPGO>true</TieredPGO>
1052
+
</PropertyGroup>
1053
+
```
1054
+
1055
+
### UseWindowsThreadPool
1056
+
1057
+
The `UseWindowsThreadPool` property configures whether thread pool thread management is delegated to the Windows thread pool (Windows only). The default value is `false`, in which case the .NET thread pool is used. For more information, see [Windows thread pool](../runtime-config/threading.md#windows-thread-pool).
1058
+
1059
+
```xml
1060
+
<PropertyGroup>
1061
+
<UseWindowsThreadPool>true</UseWindowsThreadPool>
1062
+
</PropertyGroup>
1063
+
```
1064
+
1032
1065
## Reference-related properties
1033
1066
1034
1067
The following MSBuild properties are documented in this section:
Copy file name to clipboardExpand all lines: docs/core/runtime-config/threading.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Threading config settings
3
-
description: Learn about the settings that configure threading for .NET Core apps.
3
+
description: Learn about the settings that configure threading for .NET apps.
4
4
ms.date: 11/04/2021
5
5
ms.topic: reference
6
6
---
@@ -99,7 +99,7 @@ Project file:
99
99
- For projects on Windows, configures whether thread pool thread management is delegated to the Windows thread pool.
100
100
- If you omit this setting or the platform is not Windows, the .NET thread pool is used instead.
101
101
- Only applications published with Native AOT on Windows use the Windows thread pool by default, for which you can opt to use the .NET thread pool instead by disabling the config setting.
102
-
- The Windows thread pool may perform better in some cases, such as in cases where the minimum number of threads is configured to a high value, or when the Windows thread pool is already being heavily used by the app. There may also be cases where the .NET thread pool performs better, such as in heavy I/O handling on larger machines. It is advisable to check performance metrics when changing this config setting.
102
+
- The Windows thread pool may perform better in some cases, such as in cases where the minimum number of threads is configured to a high value, or when the Windows thread pool is already being heavily used by the app. There may also be cases where the .NET thread pool performs better, such as in heavy I/O handling on larger machines. It's advisable to check performance metrics when changing this config setting.
103
103
- Some APIs are not supported when using the Windows thread pool, such as <xref:System.Threading.ThreadPool.SetMinThreads%2A?displayProperty=nameWithType>, <xref:System.Threading.ThreadPool.SetMaxThreads%2A?displayProperty=nameWithType>, and <xref:System.Threading.ThreadPool.BindHandle%28System.Runtime.InteropServices.SafeHandle%29?displayProperty=nameWithType>. Thread pool config settings for minimum and maximum threads are also not effective. An alternative to <xref:System.Threading.ThreadPool.BindHandle%28System.Runtime.InteropServices.SafeHandle%29?displayProperty=nameWithType> is the <xref:System.Threading.ThreadPoolBoundHandle> class.
- Configures whether hardware acceleration is used for WPF apps that are accessed through Remote Desktop Protocol (RDP). Hardware acceleration refers to the use of a computer's graphics processing unit (GPU) to speed up the rendering of graphics and visual effects in an application. This can result in improved performance and more seamless, responsive graphics.
16
+
- If you omit this setting, graphics are rendered by software instead. This is equivalent to setting the value to `false`.
0 commit comments