Proget and Packages()

[Philipp]

we have a problem with Proget it shows nothing at:

nuget / test / packages () $filter=(substringof(%27application%27,tolower(Id))%20or%20((Title%20ne%20null)%20and%20substringof(%27application%27,tolower(Title))))%20and%20(IsLatestVersion%20or%20IsAbsoluteLatestVersion)&$top=10

packages() is standard function of nuget or?
please can you help

Product: ProGet
Version: 3.0.0

[Alex]

Are you getting an error from nuget.exe client, or another nuget tool?

Or, is this simply not returning the results you are looking for?

[Philipp]

I get no error

Proget returning an empty result and I don't know why

[Tod]

The following query works fine on our test server:

http://proget/nuget/Default/Packages()?$filter=(substringof(%27application%27,tolower(Id))%20or%20((Title%20ne%20null)%20and%20substringof(%27application%27,tolower(Title))))%20and%20(IsLatestVersion%20or%20IsAbsoluteLatestVersion)&$top=10

It looks like the question mark is missing from your query after Packages().

[Philipp]

Hi guys I tried your link and its the same I get an empty result.

this ist the result from
https://nuget.test-dev.net/nuget/test/Packages()?$filter=(substringof(%27application%27,tolower(Id))%20or%20((Title%20ne%20null)%20and%20substringof(%27application%27,tolower(Title))))%20and%20(IsLatestVersion%20or%20IsAbsoluteLatestVersion)&$top=10

result:
<feed xml:base="https://nuget.test-dev.net/nuget/test/" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns="http://www.w3.org/2005/Atom"> <title type="text">Packages</title> <id>https://nuget.test-dev.net/nuget/test/Packages</id> <updated>2014-04-02T06:41:40Z</updated> <link rel="self" title="Packages" href="Packages"/> </feed>

[Karl]

What results do you want to see? Are there actually packages in your feed that should be returned by your query? What do you see if you browse the Packages() URL without a filter? http://proget/nuget/Default/Packages() ?

[Philipp]

we fixed our problem. after many tests we found out that we must use the absolute name of the package "CompanyName.Project.Common.Application" and not only application.