Open AlbertoBN opened 3 years ago
Found a workaround in the import script replace
Write-Host "nuget.exe push -Source $destination ""$path""" & nuget.exe push -Source $destination $path
With
Write-Host "dotnet push -k <apikeyifyouhave> -s $destination ""$path""" & dotnet push -k <apikeyifyouhave> -s $destination ""$path"""
Maybe the documentation is outdated?
Describe the bug
I have a local storage feed run under Nuget.Server. I am trying to upgrade to BaGet and no matter what I do I get an error. BaGet is running behind IIS. Tried in console and IIS mode with no results
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Packages are pushed and visible in BaGet UI
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Console error