Build warnings in Release 13.2.0 #12098

henriksorensen created 3 months ago

I have notice a number of build warning generation with the latest Asp.Net Zero release, see below. In our team we normally treat warnings as errors and we would appreciate a solution without build warnings (and no known code issues/code smells).

Please assist us by fixing these issues for the next release.

Br. Tom

aspnet-core\src\TAP.GO.Core.csproj : warning NU1902: Package 'Azure.Identity' 1.11.2 has a known moderate severity vulnerability, https://github.com/advisories/GHSA-m5vv-6r4h-3vj9
aspnet-core\src\TAP.GO.Application.Shared\Authorization\Accounts\Dto\ResetPasswordInput.cs(61,34,61,35): warning CS0168: The variable 'e' is declared but never used
aspnet-core\src\ TAP.GO.Application\Authorization\LogInManager.cs(54,51,54,73): warning CS0114: 'LogInManager.CreateLoginResultAsync(User, Tenant)' hides inherited member 'AbpLogInManager<Tenant, Role, User>.CreateLoginResultAsync(User, Tenant)'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword. *aspnet-core\test\TAP.GO.Test.Base\GOTestBaseModule.cs(50,13,50,66): warning CS0618: 'IAbpAutoMapperConfiguration.UseStaticMapper' is obsolete: 'Automapper will remove static API. See https://github.com/aspnetboilerplate/aspnetboilerplate/issues/4667
aspnet-core\src\TAP.GO.Web.Host\Startup\AuthConfigurer.cs(52,21,52,52): warning CS0618: 'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes

3 Answer(s)