Unfortunately Microsoft does not provide this information available in the feed; it's only available for viewing on NuGet.org through a special partnership with third-party software vendor SonaType. This information is proprietary, and only available when purchasing software from SonaType.

Thanks, Tod. That works. I appreciate it!

In our testing, we couldn't get the maven feed to crash, but I was able to get an "invalid response" error in Google Chrome when requesting a snapshot from a connector, and I did notice that requesting an old version of a snapshot 404s because ProGet finds the correct version number and then overrides it with the latest version number. We're still investigating...

ProGet will not give this error code, so it's coming from another tool/service in between NuGet.exe and ProGet software. Please disable WebDAV, and any other things sitting in front of the ProGet server that would issue a 405 before relaying the request to ProGet.

Unfortunately there's not enough information.. or a question here.. for us to be able to provide a meaningful answer. If this just happens as a one off, please ignore it. if it's preventing you from doing something, please describe in deatail what you're trying to do. I already see some strange things, such as "port 44300" that make the set-up seem not very obvious, so please describe that too.

It's certainly planned on our end, but because it would require a major change to the way we do package indexing, which is a significant risk and thus could impact a lot of our enterprise customers.

Generally, you "subscribe" to a feed to get notifications; however, there will be a "webhook" feature coming soon that will allow you to send webhook notifications to other tools. We will be posting more information about it soon... stay tuned.

Sorry on the delayed response, but a re-written directory provider is now available in ProGet 4.8; this should support multiple domain searching, and is in the open source InedoCore extension, so it should be a lot easier to see precisely what's going on how to debug it.

As far as we can tell, ProGet has never returned a 409 response from that endpoint. A quick Google search reveals this NuGet bug: https://github.com/NuGet/Home/issues/2910 You can fix this by upgrading to NuGet.exe 3.4.5, NuGet.exe 3.5.0-beta2, or a later version.

It sounds like your load balancer is somehow trying to interact with the Docker protocol in some manner... there's nothing on the ProGet side that should cause that message in the client. It's hard to say, however, given that the load-balancer is forwarding requests to the ProGet software..

You are using it correctly; there is a bug in that particular endpoint that ignores the variables for non-legacy plans, see: Issue BM-3077

Hello Megha, In PowerShell, to create a JSON object key with a dollar sign in it, you need to use this syntax: "`$KeyName" So your object would look like this: $CreatePackageParam= @{releaseNumber=$ReleaseNumber; applicationName=$ApplicationName; "`$SiteName"=$SiteName; } Otherwise, PowerShell replaces both instances of $SiteName with the value in that variable.

I was trying the Otter instructions link provided by you. When we execute step 4 and try to execute command: “InedoAgentService.exe install” We get the error message saying that InedoAgentSVC already exists.. attempting to uninstall it. Which means it first removed the already existing and running InedoAgentSVC and then created the same again. But it could not install it since I checked in services.msc and there was no such service(i.e, the already existing service was gone). I tried to do it as below as well: Since the InedoAgentSVC(Inedo agent service) had already uninstalled, I tried to install it again but this time with different port(used 8080 instead of 46336) so that we can use port 46336 for second agent installation as per otter instructions. I changed the port for Inedo agent and the service was installed successfully but its name was still InedoAgentSVC, so I tried to change name of service to InedoAgentSVCMain in app_appsettings.config and installed the Inedo agent again. It did not get installed and threw error. The point that comes out is that both Otter and Inedo Agent generate same service with name InedoAgentSVC. If we install either of these and then try to install the other one, the first one gets uninstalled. So as a conclusion, we can have only one of these agents in a machine. Please let me know if I am missing something or some step as I am still not able to use multiple agents on same service box.

Ah ha! Thank you so much. I'll look in to this right now :)

Nevermind, I had to grant the Feeds_AddPackage privilege to the Anonymous User.

See: https://stackoverflow.com/questions/45063717

I created a ticket with Paket, and they did resolve the issue via an update to their code base. Testing with version 5.6.6 seems to have fixed the issue. https://github.com/fsprojects/Paket/issues/2466

In Properties, @(type: txt, sha1: <sha1 value>, md5: <md5 value>, name: Artifact7.txt) should be @(%(type: txt, sha1: <sha1 value>, md5: <md5 value>, name: Artifact7.txt)). If you're more used to JSON, those are equivalent to ["type: txt","sha1: <sha1 value>","md5: <md5 value>","name: Artifact7.txt"] and [{"type":"txt","sha1":"<sha1 value>","md5":"<md5 value>","name":"Artifact7.txt"}], respectively.

A connector will transparently mirror all of the feed, including pre-release versions. So, if you don't want to see pre-release, then disable your connectors to NuGet.org or use multiple feeds.