New issue
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
Cannot restore packages from teamcity nuget server #19
Comments
@prabhakarreddy1234, which TeamCity version do you use to host nuget feed?
If response contains your package, please define internal property |
I am using I tried to access the link which you provided but getting the below response. I can access Full .Net Framework packages from the same folder in Teamcity Nuget. But not I used my local nuget store before and it's working fine. I can push and restore easily. Not sure why Teamcity doesn't display the pushed packages in both |
@prabhakarreddy1234, ok, it seems that you have disabled guest authentication in your feed. |
Actually earlier i tried with |
@prabhakarreddy1234, thanks for details. It seems like a bug in TeamCity 9.1.x. Latest TeamCity 10.0.2 version contains lots of nuget-related fixes and improvements. If could not do that, you can try to latest nuget plugin version and install it as additional TeamCity plugin. |
I will try that and let you know the result in a few days. |
Latest nuget plugin which you suggested didn't work with TeamCity 9.1.x. So i upgraded to Teamcity 10.0.2. Now i can see .net core package when i browse But in Visual studio 2015 update 3 , Nuget 3.5.0 i cannot see the package in |
@prabhakarreddy1234, could you please try to use nuget plugin with a compatibility fix for nuget 3.4+: |
From @prabhakarreddy1234 on September 28, 2016 10:29
I am using teamcity as my nuget feed. I published 1 dotnet core package using TeamCity CI. I can see that nuget package has been dropped into the nuget feed folder in Teamcity. But cannot restore that package using visual studio or command line.
I used
dotnet pack
command.Copied from original issue: JetBrains/teamcity-dotnet-plugin#19
The text was updated successfully, but these errors were encountered: