That option unfortunately will not work at this time without significant changes, and it's supposed to be hidden currently. We may remove it in the next version or add the required functionality to get it working in an even later version. The problem with it is that dependencies can now vary based on other factors such as platform, .NET Framework version, etc. As a workaround, enabling caching for the feed and downloading the package from Visual Studio will accomplish essentially the same thing, though.

Please see: http://inedo.com/support/kb/1021/using-proget-with-nuget-the-visual-studio-extension

Retention Policies are not inclused in the free edition. You can still delete packages manually however.

Another quick way you can close all connections to the database: ALTER DATABASE [DbName] SET OFFLINE WITH ROLLBACK IMMEDIATE ALTER DATABASE [DbName] SET ONLINE

It was execution time in web.config. Thanks for help!

Thank you for the report, this will be resolved in the next release.

4.0 is available for download now; we've tested it about as far as we can, the main reason it's still considered "beta" is to see how the Docker/installation process works in the wild. So, please give it a try. Depending on the requirements of non-AD LDAP, if it's easy to do, we can implement it quite soon.

VPN will occur at a much lower level than ProGet operations (which is HTTP/IIS), so I suggest you use a tools like Wireshark to dig a little further and see where the problem might be.

All of our installers are signed, our build process is isolated, and we do frequent network scans -- so it's definitely not a virus. If you want to verify it yourself, you're welcome to use a tool like .NET Reflector; it's just managed code and is not obfuscated in any way. It's just a self-contained SQL change script distribution package generated by our BuildMaster product. Still, every once in a while we get some part of the installer flagged by an AntiVirus scanner. Usually it's bmdbupdate.exe, since that does some "questionable-looking" things to an antivirus engine, such as embedding its dependency assemblies as resources. Please let them know about the false positive; the more people who do, the greater the chance they won't flag these in the future. Thanks for letting us know!

The story continuous :) Because I set TeamCity to create source packages as well (it's a checkbox called: Include sources and symbols) it was overwriting the packages in ProGet (I have all the PDB and sources in my nuspec files as well). This was causing the issue with the config file being gone, because TeamCity strips those files out for the symbols packages. So... I was doing things twice... Must be user error ;)

As of 3.5, these are the features not available in the free edition: Active Directory / LDAP Integration Filter Packages by Name & License Load Balancing & High Availability Granular Privileges & Security (scoping by individual feeds) MyGet Feed Sync

Hi Just wondering if this issue was resolved ? Pod

Hi Dean, Sorry I continued trying and found out the problem was caused because I had to include the -k flag (for HTTPS) and to include the username and password in the URL. Problem solved. Thanks. Kevin

You can just back-up the database, restore it on the new server, and edit the connection strings in the appSettings config files for the web and service.

Thank you for the cache tip. I've included -NoCache modifier to a command, and ProGet asked me about credentials.

Hi Dean Restarting the ProGet service solved the problem. Thanks!

It seems to be more stable now, or I can at least see the NuGet page on ProGet. Thanks.

Unfortunately not, but this would be a great place to post it if you are able to get it working! :) But before you do that, check under Advanced Settings to see if modifying the Base Odata URL field will solve the problem you're looking for.

I don't think you're doing anything wrong, but based on this, and your previous error... it sounds like you've got some server/network oddities. That could be any one of a THOUSAND things, but it's definitely not ProGet nor the NuGet clients. So, I'd suggest to put some wireshark or fiddler monitoring in between to see exactly what's happening, where they are coming from, and what the actual responses are.

This should be fixed in v4.5.7 (select NuGet or Chocolatey feed as the first option, and you can change the dropdown afterward). Note, we are considering deprecating the Deploy functionality in the next major version, so if you're looking to get started with deployment you should use BuildMaster instead.