Unable to push to Klondike using NuGet Package Explorer about klondike

[chriseldredge]

It looks like NuGet Package Explorer automatically appends api/v2/package to whatever URL you tell it to publish to.

http://localhost.klondike.foolhq.com/ => http://localhost.klondike.foolhq.com/api/v2/package

http://localhost.klondike.foolhq.com/api/packages => http://localhost.klondike.foolhq.com/api/pacakges/api/v2/package

None of these URIs are valid in Klondike. The correct place to put packages is to /api/packages.

I could put redirects into Klondike to work around this, but really the client should not be doing this. In my opinion this bug is in NuGet Package Explorer, not Klondike.

[leblancmeneses]

Can you add a route in web api to accept both? I don't think this is their bug. api/v2 is just saying that it is nuget v2.x compliant. The free nuget servers (filesystem) all implement api/v2 route also.

I tried adding a url rewrite but recently found out it doesn't work unless you ignore the route. RouteTable.Routes.IgnoreRoute("api/v2/{*pathInfo}"); . Either way if we want this to work in package explorer this code base is more appropriate place to resolve it.

        <rule name="Workaround for Nuget Package Explorer">
            <match url="^api/v2/package(.*)$" ignoreCase="false"/>
            <action type="Rewrite" url="/api/packages{R:1}" appendQueryString="true"/>
        </rule>

please.....

[chriseldredge]

Out of curiosity have you asked the NuGet Package Explorer developer(s) to fix this issue on their side? The behavior of their client is different from NuGet command line client, Visual Studio package manager, Package Manager Console, and even OctopusDeploy.

It seems silly to add special work-arounds for an individual client that behaves differently than everything else.

[leblancmeneses]

Just did - thanks: https://nuget.codeplex.com/workitem/4168