Pushed a package but no packages listed in Visual Studio

[markti]

So I pulled the code and modified the Nuget.Server.TestInstance with my Azure storage account connection string then published to an Azure Web App of my choosing. I appear to have successfully published a package by modifying the automation script because it shows up when I pull down the content at this url:

1: http://nuget.myserver.com/nuget/Packages

However, when I access the following URL:

2: http://nuget.myserver.com/nuget

There are no packages to be found! Visual Studio also shows no packages. Probably because Visual Studio wants to hit URL No. 2

Any ideas why the package shows up in the */nuget/Packages list but not in the */nuget list?

[purplepiranha]

I have the same issue.

I had lots of problems getting the Nuget package to work, so have downloaded the source and added it to my project. I can now upload packages to the feed and the xml looks ok, but when I try to access via VS or Nuget Package Explorer nothing is returned.

The GetPackages() function appears to be returning my packages, but they just don't appear :-(.

My feed works fine if I stop using the Azure storage and revert back to a folder under the site. I would rather use the Azure storage though.

I've also tried running locally using you're solution and the test instance has the same issue.

[purplepiranha]

Ok, so after a bit of debugging, it appears that the package metadata doesn't return correctly.

The following are not populated:
FullPath
IsAbsoluteLatestVersion
IsLatestVersion
LastUpdated
PackageHash
PackageSize
Path
Published

As a result they are not displayed in the feed correctly. Both VS and Nuget Package Manager decide not to display the package at all.

I have fudged the values in VS while debugging and managed to get the feed to work, so I'm now going to have a go at fixing the code.

I can also see that there will be an issue with downloading the package. The DownloadPackage function requires a physical path to the nupkg file (taken from metadata.FullPath). As the file is not held on the file system, then this will always fail. I'm going to try creating an AzurePackageService and then overriding this method.