Aviso do NuGet NU5129

At least one .<extension> file was found in '<build_folder>/<tfm>/', but '<build_folder>/<tfm>/<package_id>.<extension>' was not.

<extension> pode ser: targets, props. <build_folder> pode ser: build, buildTransitive, buildCrossTargeting, buildMultiTargeting. <tfm> é um Target Framework Moniker ou pode estar ausente. <package_id> é o identificador de pacote do seu pacote.

Exemplos:

At least one .targets file was found in 'build/netstandard2.0/', but 'build/netstandard2.0/MyPackage.targets' was not.
At least one .props file was found in 'build/netstandard2.0/', but 'build/netstandard2.0/MyPackage.props' was not.
At least one .props file was found in 'buildTransitive/net472/', but 'buildTransitive/net472/My.Package.Id.props' was not.
At least one .targets file was found in 'buildMultitargeting/netcoreapp3.0/', but 'buildMultitargeting/netcoreapp3.0/Contoso.Utilities.targets' was not.
At least one .props file was found in 'build/', but 'build/AdventureWorks.Tools.props' was not.

Problema

Os pacotes que incluem props e destinos do MSBuild precisam seguir a convenção de nomenclatura de usar a ID do pacote antes da extensão .props ou .targets. Os arquivos que não seguem essa convenção não serão importados para projetos que usam o pacote.

Exemplo: se a ID do pacote for Contoso.Utilities e contiver os arquivos build/Contoso.Utilities.props e build/Utilities.targets, somente o arquivo Contoso.Utilities.props será importado para projetos usando o pacote. Utilities.targets não será importado pelo NuGet.

Solução

Renomeie o arquivo para atender à convenção.

No exemplo acima, build/netstandard2.0/Utilities.targets deve ser renomeado para build/netstandard2.0/Contoso.Utilities.targets para que o NuGet comece a importá-lo. Se Utilities.targets estiver sendo importado no Contoso.Utilities.props, renomeie o arquivo para usar a extensão .props também.