It is supported with Active Directory, so you can use your domain credentials with npm, but since as far as I know the npm client does not send Windows authentication information when it makes requests, there is no way to have this happen automatically. It may be possible to fork npm and add this - say using ldapjs, but I'm not aware of any current projects like that.

Hi, I don't see any EventOccurrenceDetails in my database, and I am trying to troubleshoot why a package did not upload. I spied using Fiddler the HTTP request, and it seems I get back an Invalid API Key error. Has the schema changed? Are log files surfaced in the UI now?

Version 3.4.2 works great, thanks!

A "cached" package is a package that's stored locally so it doesn't have to be downloaded from the external feed, as opposed to a "local package" which is a package that is actually in the local feed. Packages are cached the first time they are requested from the external feed (whether that's by downloading it in the UI, or by using nuget restore, or downloaded via some other tool). Pulling a package downloads a remote package into the local feed as if you pushed it to the feed yourself, so to speak.

Hmm, it's not supposed to require outbound internet access. That should only be necessary to grab a license key, but it should make you enter one if it can't pull one from the internet.

I can't reproduce this problem; the query always works for me. Could you send a fiddler trace of the failed request to support at inedo.com?

Strange. If you open the Tools->Options->Debugging dialog in Visual Studio, is the "Require source files to exactly match the original version" item checked? If it is not checked, that may cause it to use an old source file in the debugger. As far as I know, the PDB age is part of the symbol file's unique identifier - when Visual Studio asks for symbols, it makes a request to a URL with the PDB GUID and age. I think age normally gets incremented when a project is rebuilt in Visual Studio, though I don't know the rules about this for sure. Since you get the correct symbols/source if you clear out the symbol directory, I'm guessing Visual Studio just isn't making a request to ProGet because it thinks it already has the correct files. The best thing to do in this case is to run Fiddler and capture a trace of both behaviors and see what's different. You can send us a copy of these to support at inedo.com if you want some help troubleshooting.

Yeah that's probably the best bet.

Please note that granular, feed-based security is only available in the paid Enterprise edition. In the Express edition, privileges may only be applied to the whole system. If you would like to trial these features, you can request a trial key at https://my.inedo.com

Do you by chance have a space (or other reserved character) in the feed name? If so, make sure it is URL encoded when you access it, e.g.: http://domain.com:81/nuget/Feed Name With Spaces

Proget 3.4.4 Visual Studio fetches the PDB correctly to the symbols cache, but then searches for the source with a local path used on our build server. Sources are not downloaded.

PyPI support has been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

v3.3.11 has been released that should resolve this issue.

ProGet does index those source files, for both C# and C++. Are you having a problem with this, and if so, can you provide some repro steps?

I just installed v 3.4.6 Build 6 and it is now working. I used SQL Express installer this time instead of connecting to a stand alone sql server. Not sure if that made any difference.

Hi again. I found that if i Grant AND Deny the Anonymous user "View Only" privilege then everything is fine.

v3.3.11 has been released that should resolve this issue.

I did solve my problem with installing and reinstalling proget. Now is everything working.

OK, I've upgraded the feeds to the ProGet 3.3 format (there was still in legacy format), and I have been able to successfully apply your workaround proposition. It's not ideal but it's working.

I assume the internet is not accessible from the server that ProGet is installed on? Either way, try setting the UpdateCheck_Next setting on the Advanced Settings page to an empty value.