Setup app insight in web api (#110) #34
Annotations
11 warnings
|
Build with dotnet:
blotztask-api/Data/Seeding/BlotzContextSeed.cs#L49
Possible null reference argument for parameter 'user' in 'Task<IdentityResult> UserManager<User>.AddClaimsAsync(User user, IEnumerable<Claim> claims)'.
|
|
Build with dotnet:
blotztask-api/Data/Seeding/BlotzContextSeed.cs#L94
Dereference of a possibly null reference.
|
|
Build with dotnet:
blotztask-api/Data/Seeding/BlotzContextSeed.cs#L105
Dereference of a possibly null reference.
|
|
Build with dotnet:
blotztask-api/Program.cs#L63
Possible null reference argument for parameter 'uriString' in 'Uri.Uri(string uriString)'.
|
|
Build with dotnet:
blotztask-api/Services/TaskService.cs#L38
The variable 'ex' is declared but never used
|
|
Build with dotnet:
blotztask-api/Data/Entities/User.cs#L6
Non-nullable property 'TaskItems' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
blotztask-api/Data/Entities/TaskItem.cs#L10
Non-nullable property 'Title' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
blotztask-api/Data/Entities/TaskItem.cs#L11
Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
blotztask-api/Data/Entities/TaskItem.cs#L16
Non-nullable property 'UserId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
blotztask-api/Data/Entities/TaskItem.cs#L18
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
dotnet publish
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.
|
Loading