We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run nuget push bin\Release*.nupkg -source https://api.nuget.org/v3/index.json -SkipDuplicate Pushing TimeSeriesAnalysis.1.3.21.nupkg to 'https://www.nuget.org/api/v2/package'... PUT https://www.nuget.org/api/v2/package/ Created https://www.nuget.org/api/v2/package/ 599ms Your package was pushed. Pushing TimeSeriesAnalysis.1.3.21.snupkg to 'https://www.nuget.org/api/v2/symbolpackage'... PUT https://www.nuget.org/api/v2/symbolpackage/ BadRequest https://www.nuget.org/api/v2/symbolpackage/ 152ms Response status code does not indicate success: 400 (The package does not contain any symbol (.pdb) files.). Error: Process completed with exit code 1.
Is the error message
run the CreatePacakge.bat file in \scripts and it is true that no pdb file is created during the build.
This is strange as the build is
dotnet pack TimeSeriesAnalysis.sln -c Release --include-symbols -p:NuGetBuild=True -p:SymbolPackageFormat=snupkg --include-source
and the TimeSeriesAnalyis.csproj file includes
true
The text was updated successfully, but these errors were encountered:
tried to debug #142, but to no ovail
801d694
Revert "tried to debug #142, but to no ovail"
2cd165c
This reverts commit 801d694.
No branches or pull requests
Is the error message
run the CreatePacakge.bat file in \scripts and it is true that no pdb file is created during the build.
This is strange as the build is
dotnet pack TimeSeriesAnalysis.sln -c Release --include-symbols -p:NuGetBuild=True -p:SymbolPackageFormat=snupkg --include-source
and the TimeSeriesAnalyis.csproj file includes
true
The text was updated successfully, but these errors were encountered: