| Severity | Warning |
| Reported by | PostSharp |
| Message | <Reason> |
Cause
A repository can opt out of the usage reporting (telemetry) of PostSharp for all its builds, with the TelemetryEnabled property in the postsharp.config file at the root of the repository:
<Project xmlns="http://schemas.postsharp.org/1.0/configuration">
<Property Name="TelemetryEnabled" Value="False" />
</Project>
This setting is read by the telemetry services of PostSharp, not by the PostSharp compiler, and they read it with stricter rules than the compiler applies to the other properties. When they cannot use the setting, they ignore it, and the default telemetry policy applies to the build. PostSharp then reports PS0284, so that the repository knows that it is not opted out. <Reason> is a complete sentence that names the file and says why it is ignored. The usual causes are:
- The value is not one of the literals
TrueandFalse, but an expression, for example one that refers to another property. - The
Propertyelement has a condition, or the property is defined more than once. - The setting is in a
postsharp.configfile below the root of the repository.
The warning is located at the file, when the reason concerns a file.
This message depends on the configuration files of the repository and on the telemetry services of the machine, so no example can show it.
Resolution
- Write the
TelemetryEnabledproperty once, in thepostsharp.configfile at the root of the repository, with the literal valueTrueorFalse, without a condition, as shown above. - Remove the property from the
postsharp.configfiles below the root of the repository. - To opt out on a machine rather than for a repository, for example on a build agent, set the
POSTSHARP_TELEMETRY_OPT_OUTenvironment variable instead.
See What's New in PostSharp 2027.0 for how telemetry works in this version of PostSharp.
See Also
Other Resources
What's New in PostSharp 2027.0
Configuring Projects Using postsharp.config
Well-Known Environment Variables