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).

Hi, Thanks for the bug report; this will be addressed in the next release of ProGet, which is due in just a few days!

The service does need to be running mainly to index packages. If you selected the IIS option during install, the web server in the service will not run. If you are switching from integrated web server to IIS, make sure to update the service's .exe arguments to exclude the /urls argument and then the web server component of the service will not run.

For completeness, v3.0.3 was just published which adds an index to Publish_Date and the dashboard query now returns virtually instantly tested against 100,000+ packages in the database.

I didn't run it as an admin, but I think it popped up the UAC prompt. Also, it managed to delete most of the contents of the proget directory in program files. Unfortunately, that's all the info I've got. Hope it helps you out.

Unfortunately at this point, we have no good examples of this sort of thing. You might be able to get away with inheriting from DirectoryPackageStore and extending its behavior on EnableChangeNotifications() to add your own FileSystemWatcher, but it all seems unnecessarily complicated when a simple scheduled task would do the trick.