There have been a few modifications since the version you're running to the symbol/source server that will likely fix the behavior you're experiencing. There is one issue in particular that involved reverse sorting of the symbol file's age value that I believe is related. When you upgrade to the latest, it should resolve the issues.

Ok, it worked. If after created a connector the app asked to index and redirect to the scheduled task, it will be nice.

I would use .NET 4.5 with NuGet.exe to be safe.

Nevermind, apparently, the installation was messed up because of the failed previous upgrades (due to the antivirus). The program was not registered anymore so the installer didn't detect it for upgrade. I simply installed over the previous installation and it worked! Now running on 4.0.9! Thanks a lot for the info and help!

I assume, you are looking to deploy a package for deployment later? If this is the case, take a look at this guide, which goes over how to package and deploy an application for deployment using Otter. Otherwise, you can just use standard NuGet.exe client tools to package and publish your packages to the ProGet feed

The privileges are cached; if you "invalidate cache" on the privileges page or restart the web application, that should fix it.

ProGet supports the latest versions of all the major browsers. However, please note that only IE v11 is supported by Microsoft. We do test in IE9, and offer limited support. IE8 and earlier will probably exhibit some issues, but will mostly work most of the time; we do not test with those anymore.

I was able to get this working. I had to change the license key to something else and save it, then change it back to the proper key and save it again. Once I did that, it asked me to manually validate.

Hi TJ, That upgrade path is fine, and quite common; as long as the shared storage is the same (I assume it's already a UNC path), then when you start everything up again (webserver, indexing service), it should be the same. There isn't so much risk going from 3.5 -> 4.0, but please do read the ProGet upgrade notes just to see what's coming. Just make sure to do a quick test on the current (2005/single server) set up as 4.0 before moving that to new servers. You can always rollback if there is a realy big issue (though, we haven't seen any yet!) Best, Alana

In short, don't use the wizard, we have decided to remove them in v5 anyway because of problems like this. Instead, simply create a Standard Application, and then visit the Workflows tab, and add a Build Step that imports from TFS. That's actually all the wizard is supposed to do anyway.

This is a pretty common deployment for BuildMaster; there are a lot of options, but the easiest thing we've seen is to do the "exploded WAR" strategy -- basically, unzip the war file into the catalina_home directory, and kick the tomcat service. This saves a lot on initial load time as well.

Not in particular, but you might find limitations on intermediate network equipment when you try to download very large files (just like you might from over any web/HTTP point).

I managed to perform the upgrade. I had to stop IIS before running the process and run the following command: ProGetSetup4.0.9.exe /Upgrade /S /BackupDatabase=false

It's a false positive; see KB#1113 - Anti-malware False Positives, Code Signing, and Safety of Inedo Products for more information. Please let your malware protection provider know about the false positive; the more people who do, the greater the chance they won't flag these in the future.

Thanks. I want that Administrators won't do it either to prevent accidental problems.

Take a look at the Getting a Simple Application into BuildMaster Tutorial for a good way to get started!

Well, there is literally no js error since the browser loads forever and never returns. There is also no logs in the admin section.

If you have locked yourself out of ProGet, then you can use ProGet.Service.exe to reset the Admin account.

The easiest option is to put them directly in the URL of the repository: https://username:password@domain/

This error is coming from NuGet.org; unfortunately, certain long quriers will sometimes cause that error. It's intermittent. This is planned to be addressed with an "offline package index" in a future proGet release.