question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. ItĀ collects links to all the places you might be looking at while hunting down a tough bug.

And, if youā€™re still stuck at the end, weā€™re happy to hop on a call to see how we can help out.

Nullable csproj element still not supported in preview6?

See original GitHub issue

In the docs for Nullable reference types it says:

The Nullable element was previously named NullableContextOptions. The rename ships with Visual Studio 2019, 16.2-p1. The .NET Core SDK 3.0.100-preview5-011568 does not have this change. If you are using the .NET Core CLI, youā€™ll need to use NullableContextOptions until the next preview is available.

Iā€™m now using 3.0.100-preview6-012264 and the Nullable element is still not working and Iā€™m having to use NullableContextOptions. It wouldnā€™t be a problem except that Iā€™m recording tutorial videos for .NET Core 3.0, so I have to keep changing the element to Nullable when Iā€™m recording edits to csproj files and then back to NullableContextOptions before I run things using the CLI.

Do the daily preview7 builds support the new element name yet? Or is there some other way I could get it working? Or am I asking in the wrong place and I should go bother the Roslyn folks?

P.S. I appreciate that ā€œIā€™m recording tutorial videos using preview bits and I need to donā€™t want to have to re-record a bunch of stuff because changesā€ is not a broadly applicable use case, so I donā€™t expect this to be a high priority issue or anything. I just thought Iā€™d ask.

P.P.S. I canā€™t use Visual Studio 16.2-p, because Iā€™m teaching people to use the CLI like proper programmers from the 1980s, when the world was simpler and if you forgot how to exit vi you had to go and find another terminal so you could run man vi and write down the mystic sigils.

P.P.P.S. No, Iā€™m not going to make my .NET Core 3.0 tutorials in the form of man pages because itā€™s 2019 and that would hurt sales, so donā€™t be silly.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
agockecommented, Jul 2, 2019

@nguerrera Yeah that doesnā€™t look good. Letā€™s not do that again.

0reactions
agockecommented, Jul 2, 2019

Actually I canā€™t close this issue. šŸ˜„ @livarcocc all yours

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to enable Nullable Reference Types feature of C# 8.0 ...
To enable Nullable Reference Types for all code in a project, add the following to its .csproj file:
Read more >
Try out Nullable Reference Types - .NET Blog
Try out Nullable Reference Types. With the release of .NET Core 3.0 Preview 7, C# 8.0 is considered "feature complete".
Read more >
Using C# 8 and Nullable Reference Types in .NET Framework
While parts of C# 8 will never be supported in .NET Framework, the Nullable Reference Types can be turned on if you know...
Read more >
First steps with nullable reference types
This blog post is effectively a log of my experience with the preview of the C# 8 nullable reference types feature.
Read more >
C# 8: Nullable References
C# 8 introduces is the Nullable reference type, which helps prevent the unhandled null reference exceptions.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found