Skip to content

Commit bce5705

Browse files
authored
Fix 41921 (#41949)
* Initial fix for 41921 * link to section anchor for nullable
1 parent d7bc994 commit bce5705

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docs/csharp/nullable-migration-strategies.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ If your codebase is relatively small, you can turn on the [feature in your proje
1414

1515
Regardless of how you update your codebase, the goal is that nullable warnings and nullable annotations are enabled in your project. Once you reach that goal, you'll have the `<nullable>Enable</nullable>` setting in your project. You won't need any of the preprocessor directives to adjust settings elsewhere.
1616

17+
> [!NOTE]
18+
> You can designate a `Nullable` setting for your project using a `<Nullable>` tag. Refer to [Compiler options](language-reference/compiler-options/language.md#nullable) for more information.
19+
1720
The first choice is setting the default for the project. Your choices are:
1821

1922
1. ***Nullable disable as the default***: *disable* is the default if you don't add a `Nullable` element to your project file. Use this default when you're not actively adding new files to the codebase. The main activity is to update the library to use nullable reference types. Using this default means you add a nullable preprocessor directive to each file as you update its code.

0 commit comments

Comments
 (0)