Skip to content

Conversation

@jimmyca15
Copy link
Member

  • missing project inclusion in solution file
  • Project declared nullable support but wasn't written with it in mind
  • pack.ps1 script didn't reference newest project.

* missing project inclusion in solution file
* Project declared nullable support but wasn't written with it in mind
* pack.ps1 script didn't reference newest project.
@zhiyuanliang-ms
Copy link
Member

zhiyuanliang-ms commented Nov 8, 2023

<OutputType>Exe</OutputType>
<TargetFramework>net6.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any reason that we keep the enables in the RazorPages example?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because that project was made with nullable in mind. It uses it correctly. The other projects don't use nullable in the code, and it seems it was added into csproj after the fact causing compiler warnings.

@jimmyca15
Copy link
Member Author

@zhiyuanliang-ms any further concerns on this PR?

@zhiyuanliang-ms
Copy link
Member

@jimmyca15 I have no further concerns about this PR.

@jimmyca15 jimmyca15 merged commit e91fdbd into microsoft:preview Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants