Skip to content

Nullness issue - support direct <Nullable>enable</Nullable> flag instead of <OtherOptions> #17403

@T-Gro

Description

@T-Gro

Issue description

The <Nullable>enable</Nullable> msbuild property is used in C# already.
Since this feature is targeted at interop scenarios, it would be handy to support the exact same property, since people can have it in their Directory.* files for the whole solution.

Choose one or more from the following categories of impact

  • Unexpected nullness warning (false positive in nullness checking, code uses --checknulls and langversion:preview).
  • Missing nullness warning in a case which can produce nulls (false negative, code uses --checknulls and langversion:preview).
  • Breaking change related to older null constructs in code not using the checknulls switch.
  • Breaking change related to generic code and explicit type constraints (null, not null).
  • Type inference issue (i.e. code worked without type annotations before, and applying the --checknulls enforces type annotations).
  • C#/F# interop issue related to nullness metadata.
  • Other (none of the categories above apply).

Operating System

Windows (Default)

What .NET runtime/SDK kind are you seeing the issue on

.NET SDK (.NET Core, .NET 5+)

.NET Runtime/SDK version

No response

Reproducible code snippet and actual behavior

<Nullable>enable</Nullable>

Possible workarounds

<OtherFlags>--checknulls+</OtherFlags>

Metadata

Metadata

Assignees

Labels

Area-NullnessIssues related to handling of Nullable Reference TypesArea-ProjectsAndBuildMSBuild tasks, project files, framework resolution

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions