Thanks for letting us know, @hwittenborn We must not have the http --> redirect setup in our DR server , we'll try to get that soon

Hi @marc-ledent_9164, Thanks for following up and letting everyone know that this fixed your issue! Thanks, Dan

Hi @marc-ledent_9164, Thanks for following up and letting us know that fixed the issue. We are currently in the process of cleaning up our activation process in the v2022 versions of our products. This issue should be corrected in the next major version of our products. Thanks, Dan

You can ignore this error; for whatever reason, the NuGet client unexpectedly terminated the connection, and the result was that ProGEt stopped writing bytes. Not really anything to worry about. The diagnostic center isn't for proactive-monitoring, more for diagnostic purposes. So ulnless users are reporting a problem, you don't need to check it.

@rmusick_7875 generally speaking feed information is combined from chocolatey.org (and other connectors you configure), metadata stored in the database (the NuGet* tables), and cached/local package files on disk

@Dan_Woolf Thanks for the explanation. I'll try it as soon as I can re-activate my trial license...

Hi @alin-kovacs_4228 , We don't maintain documentation for that version I'm afraid; the Native API is available, and you can find it in the software with /reference/api However, your best bet would be to work with our team to figure out what you need to do and get some help migrating to a newer version or something :) Cheers, Alana

Awesome! Thanks for the quick reply!

Thanks for the answer, I'll ask the team!

Hello @bkohler_1524, Because packages are immutable, you need to decide the future-compatibility at the time you create the package. This is where Semantic Versioning dependencies can really help. Following the rules of SemVer, you can say that "ProductA 1.0.0 has a dependency on ProductB (1.1.0-2.0.0]", what that means is that you can use every version of ProductB from 1.1.10 up to (but not including) 2.0.0. This allows you to make as many minor versions of ProductB (such as 1.200.0) before "breaking" compatibility. If these version numbers are business/marketing-driven, and it's impossible to change their mind on versioning, you can always maintain an internal version number - this is what many products (such as Microsoft) does.

Hi @nuno-ildefonso_8876 , Thanks for that information; this will be fixed in the next maintenance release (BM-3788), later this week (on Friday).

Thank you, @rhessinger, for clarification. Yes, I use common blob storage, and all that makes sense now.

Good news

Hi @testing-avram1_6229, Can you please tell me what version of BuildMaster you are using and what version of the BuildMaster agent you have installed? Also, if you change the BuildMaster agent to a Delayed Start instead of an Automatic start on your remote server, do you see the same issue? Thanks, Rich

Hi @NUt , Thank you for bringing this to our attention. This bug, PG-2126, will be fixed in ProGet 6.0.12. Going forward it will allow you to configure everything and even test it via the "Test User Directories" button, but it will only allow you to login using the Built-In user directory and the username/password login option when using ProGet free. Thanks, Rich

Hi @afd-compras_2365 , This is the second request for the feature - but I'll bring this up at our engineering meeting. @benjamin-soddy_9591 is there something more you can add to the conversation ? Cheers Nanci

hi @ab-korneev_0401 , By "debugging", we mean running the ProGet code inside of Visual Studio's "debug mode". That will show the errors let us see quickly how to fix them. I'm afraid it's not easy to identify the problem without it, since it's very likely a bug in the third-party repository you're using. Since it's not possible to provide that information, can you... create a server on AWS LightSail (or similar cloud service) Install the same type of third-party repository software and configure it in same manner upload one or two packages that reproduce the problem verify the problem in ProGet Then, send us the information of the server, and we can look at it through the debug mode

Hi @dm-sidelnikov_5266, Glad to hear it! Please let us know if you have any other questions. Thanks, Rich