That's correct in that it's too early to read the file, which is why it results in the sharing violation (the file is opened for write by w3wp.exe without FileShare.Read). The new file in the directory triggers the FileWatcher (which doesn't find the file because it's not completely written yet). However, the NotifyChangeDirectory operation in the feed directory will trigger the FileWatcher again after the file is completely written and closed in which case it would get picked up by the indexer, and that would make the package appear in the feed. Is there a way to run the monitor again to cross-reference the times that the error appears in the ProGet error log with a violation within the Process Monitor log? I am thinking that these particular sharing violations are not related to the errors you're seeing.

That sounds great, thanks a lot!

Oh I see what you mean - I thought you meant that you were able to upload packages using the NuGet client... I was able to reproduce in that way. We'll have a fix for this in maintenance release v3.0.4 (logged as issue PG-210). Apologies for the confusion.

Yes, although you may get some file read errors if someone happens to be downloading the exact package that's being backed-up or copied. Many back-up processes/tools will do things like shadow copy and limited read handles to prevent this from happening.

Thanks so much! This has been logged as PG-208, and we plan to fix in the upcoming maintnence release (3.0.4)

Thanks for the report - we are able to repro and will fix it in the next maintenance release.

Hmm, not sure, but it sounds like the problem is a corrupt install package? That's a error thrown from within MSI extraction. Maybe try downloading the file again.

We will add the descriptions at some point (we have them in BuildMaster). The HTML should probably be in a div, as it renders the value as a literal string. You can try it with something like: <div class="white-box padded-box"><h2>{Company} ProGet Repository</h2><p>Welcome to our collection of ProGet feeds.</p></div>

This sounds like it's related to package indexing. Please see this StackOverflow answer for troubleshooting steps: http://stackoverflow.com/questions/23812344/publishing-to-proget-and-i-cant-see-any-packages

This sounds like it's related to package indexing. Please see this StackOverflow answer for troubleshooting steps: http://stackoverflow.com/questions/23812344/publishing-to-proget-and-i-cant-see-any-packages

To expand on this story what we are thinking about doing is creating a wide open pass through feed to Nuget that would allow users to discover new open source software to use. By forcing users through Proget we can get user info to send them reminder emails about OSS that we have not yet cleared for use in our products. Then the devs can get it cleared etc.

Are you overwriting an existing package when this happens, or are these fresh packages that are getting uploaded? Either way, if you could send that Process Monitor output to support@inedo and reference this post that would be very helpful, thank you!

At this point in time, it is unlikely. However, Atlassian does mention on their site that plugins could be created to integrate with third-party tools, and the JSON ProGet API could be used for this.

Not as of 3.8, but there will be a UI refresh in v4.0 (due later this month) and that will no longer be in the navigation bar.

Tod, I justed tested it and it works perfectly. You can see this API being used in Fiddler when you use the "Show all versions" link for a package in NPE. Previously doing that didn't work against a ProGet feed. Thank you for the fast turn-around! That was impressive... Riko

Thanks Philipp, we've identified some additional performance issues as well and will plan to release a maintence ProGet release to fix this .. ideally today.

Unfortunately, the "Download Dependencies" feature can act a little funny because the way NuGet does dependencies is a little funny. It's on our list to improve this functionality.

Yes, just edit the connection string in both the web and services directory.

Are you using the integrated web server, or hosting via IIS? Regardless, if you don't want to just delete the ProGet database and start from scratch, you can run the following command from PowerShell or a CMD window to reset the authentication mechanism: sqlcmd -E -S localhost -d ProGet -Q "UPDATE Configuration SET Value_Text = 'false' WHERE Key_Name = 'LDAPEnabled'" You can additionally reset the Admin user by running the ProGet.Service.exe executable and selecting Action 7 "ResetAdminPassword".

To back-up ProGet, you just need to Back-up the Database and the Packages directory (the path is listed on each feed, and is in the All Settings under Admin).