Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-dotnet@v1, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Nullability of reference types in type of parameter 'voteValue' of 'Task ParticipantService.SubmitVote(string participantName, string connectionId, string voteValue)' doesn't match implicitly implemented member 'Task IParticipantService.SubmitVote(string participantName, string connectionId, string? voteValue)' (possibly because of nullability attributes).

The result of the expression is always 'false' since a value of type 'int' is never equal to 'null' of type 'int?'

Non-nullable property 'RoomName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'RoomVotingSystem' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'RoomUserStories' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Username' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Email' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Username' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Email' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'Password' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.