It's really hard to say; if it works from your browser but not from visual studio, then I recommend to run fiddler, and then see what Visual Studio is doing. Maybe it's a cached password, wrong DNS, or something. If you look at the session logs, you should be able to see how the requests are different.

The error is "The process cannot access the file 'C:\ProgramData\ProGet\Packages.nugetv2\F2\ACME.Shared\ACME.Shared.0.2.19.nupkg' because it is being used by another process." That error is coming from Win32, and will happen when another process tries to lock a file. Most likely, this other process will be an indexing service or anti-virus tool that is scanning/locking the file as soon as proGet starts writing to it.

Use https://registry.bower.io/packages as the connector URL instead of https://bower.herokuapp.com to resolve this. Bower must have changed the default service URL within the past day.

This is only supported in "new" NuGet feeds; some of our preliminary docs are here... https://inedo.com/support/documentation/proget/feed-types/nuget

Wonderful! Worked just as you said it would. Thank you very much Alana.

It certainly might... but we haven't evaluated it for performance considerations, etc. Early on, we tried implementing a much more advanced filtering system (author, versions, etc), but it really put a strain on NuGet.org and became useless, so we didn't continue on that featureset. This is the first request for this specific filter, and it might be simple, but we'll definitely consider it.

This particular issue just means that the web server and service cannot communicate; doesn't have much to do with VOR SECURITY, and you can simply resolve it by restarting the web/service.

To resolve this on our end, I had to use local paths to the extension folders instead of relative in the Advanced Settings page. I was hoping to use relative in our 3 web node NLB environment.

The /symbols/feed giving a 404 is an expected result; when you visit the page, you will get a 404, but also see instructions on how to configure visual studio. Unfortunately we're not able to reproduce this "unable to check the enable box" error, nor have any idea what might cause it. It's a simple page that sets a flag in the database.

I'm guessing that you're referring to this from the docs. I'll give it a try. ...Feed API key authentication is performed using HTTP basic authentication. To authenticate using a Feed API key, supply "api" for the user name and the API key for the password. feed api keys

Very nice to hear that. Thanks Alana.

Hi Ken, Thanks for contacting us. We are aware of this issue and have traced it to be a bug in a database script, that only affects Linux. The good news is we already have issued a fix for the problem (https://inedo.myjetbrains.com/youtrack/issue/PG-1101), it just needs to be reviewed and tested.

This would require feed-scoped privileges, which is a paid feature. See Features by Edition for more differences.

Is it a "Portal PDB"? This is the new format and is not yet supported. If not, then the next step would be for you to submit a ticket with the NuGet package attached so that we can debug the pdb parsing.

Support for portable PDBs is currently an "open issue", and our initial research found that metadata information was undocumented, however since then it has been: https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/specs/PortablePdb-Metadata.md Unfortunately at this time we don't have a timetable for if or when this gets implemented, but it is on our list.

The ProGet server doesn't modify packages, except to strip embedded symbols and source code if that option is enabled on a feed. It certainly doesn't modify a package such that the folder structure is flattened. Are you certain the package isn't flattened on the server, and in addition to that, actually being downloaded from ProGet at all (versus the NuGet cache or something like that)?

That's great news. Thanks!

You will need to open both ports; the npm api uses both HTTP and HTTPS.

You can use the following docker command: docker rmi tag-name