Most likely, Visual Studio is trying to talk to nuget.org and other services. You can use Fiddler to see what connections are being made.

There is nothing to re-index. If you see it in the web, then it's already indexed. If the packages appear on the web page, then they will appear in the feed. You can manually inspect the feed with the API if you'd like, or by using a tool like Fiddler or something to see the requests.

Hello Ryan, Sorry about the delayed response. The Push to ProGet Visual Studio extension is for Universal (upack) feeds, not NuGet (nupkg) feeds.

I had to update the NuGet feeds to the latest version after the upgrade. The packages are pulling in now.

Hello Attila, This is indeed a bug. I've filed PG-1272 to fix this.

Hello, Ben. Thank you for your reply. Test result is as you expected. The icon issue was solved after I changed backslash to forward slash. Regards.

Based on the URL -- you must have created a Universal Packages feed. You'll need to create a NuGet feed.

Hi Giorgi, Are you using Windows Authentication for your instance of ProGet? Thanks, Jason

Hi Alana This page (https://inedo.com/support/documentation/proget/core-concepts/connectors) has no info that I have to link the connector to my feed. Just add a little section at the end with a screenshot so the users sees what he has to do after creating the connector.

Hello Tom and Brett, The endpoint being requested seems simple enough. For example, here's what it requests for -StartWith Inedo.. I've filed PG-1281 to add an implementation of this endpoint.

I can't get the Visual Studio 2012 or 2013 SDK to install. In the meantime, you could try building the extension locally with the reference to the 2015 DLL changed to the 2012 or 2013 version: https://github.com/Inedo/VsPushToProGet

As of ProGet 4.7.4, we are no longer performing any server-side filtering based on target framework. Can you confirm that you are on the latest version?

Thanks Dean, upgrading to 4.7.3 has solved the issue!

This seems to be unrelated; the problem before was that ProGet was not providing a 404 when a package was not found, but instead an empty result. Also, we cannot reproduce this error at all, so it's isolated to yours. As such, please Ask a New Question as not fill this one; and also make sure to provide a stack trace of the 500 error message; this can be found in Admin > Error Logs.

By default, Visual Studio 2012 and later does not use the source server even if the PDBs contain the correct source indexing information. To enable the source server, go to Tools > Options, Debugging, General and check "Enable source server support". This is disabled by default as it's a security risk. The mechanism for the source server encodes a command to execute into the PDB file, therefore untrusted PDB files could execute arbitrary code. Users have to opt in. See "Use Source Servers" in Specify Symbol (.pdb) and Source Files in the Visual Studio Debugger for more information.

I see, while that works for some projects, not all of our projects uses a build server which complicates the process of deployment. Thanks

Believe me, we really wish it was feasible to provide "Integrated Windows Authentication" (i.e. 401/NTLM challenges) for some feeds, and "Anonymous" for others. The problem is that this is implemented at the HTTP.SYS stack level (a kernel-level service), which far below IIS. NTLM/Kerberos authentication is not something we can feasibly implement ourselves... even if we did, the TGS Exchange cannot really run in a protected environment (like an app pool user). This has been a known issue by Microsoft for at least 10 years, and they are planning to introduce some new libraries/options with Server 2016. There are rumors they will drop it altogether in favor of federated authentication (i.e. Azure style). But, it's not huge on their priority list I think.

I've got it working now, but only with the port. I'd rather not have to do that, but it will work for now. I'd really like to know why I can't use a reverse proxy in front of ProGet to avoid needing to specify port numbers.

Would love to see a VSIX feed (didn't see a way to vote for this feature).