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/

'DatabaseContext.Users' hides inherited member 'IdentityUserContext<IdentityUser, string, IdentityUserClaim<string>, IdentityUserLogin<string>, IdentityUserToken<string>>.Users'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword.

'DefaultException.Message' hides inherited member 'Exception.Message'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword.

Possible null reference argument for parameter 's' in 'byte[] Encoding.GetBytes(string s)'.

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

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

Non-nullable property 'LastName' 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.

Non-nullable property 'PasswordConfirmation' 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 'ProfilePicture' 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.