Hi @pariv_0352 We've updated ProGet 2022.6 to be more permissive and allow the . in non-semver2 NuGet versions. v2022.6 will be released on Friday. Thank you!

@NanciCalo - Thanks very much for that - all my googling was to no avail at finding that page, and all the forum posts I found were from back in 2016 when things were different... Much appreciated!

Hello, This is related to a known issue that's been addressed in ProGet 6.0.19 and ProGet 2022.5. So, your best bet is to upgrade and the issue will become resolved :) This is related to an few packages that have exceeded 2.2b downloads: Microsoft.NETCore.Platforms Microsoft.Extensions.Primitives Microsoft.Extensions.DependencyInjection.Abstractions If upgrade is impossible/difficult right way, then as a work-around, you can disable the connector. Alternatively, you could block those packages with a connector filter then upload them to your feed so that the counts won't come through the connector. Cheers, Alana

Hi @mike_2282, Thank you for the feedback. I have made some changes to the documentation to address most of the issues you have brought up. Thanks again for the feedback! Thanks, Rich

Hi all, This is a known issue, and it's addressed in ProGet 2022.6 and ProGet 6.0.19. It seems to come from these three packages: Microsoft.NETCore.Platforms Microsoft.Extensions.Primitives Microsoft.Extensions.DependencyInjection.Abstractions As a work-around, you can block those packages with a connector filter, or upload them to your feed so that the counts won't come through the connector. Cheers, Alana

@jblaine_9526 Thanks for clarifying! I think SAML integration is one of those "write-once" things, where we completely forget about how it works every time I'm not so familiar with SAML behind the scenes... do you know how "SAML group claims" work? For example... Is it something that comes back in the XML response, or does it require a separate request? What do the "group claims" look like? Like a list of human-readable group names? And them most importantly... what should ProGet do with such claims upon receipt? Treat the user as if they're in the group (kind of like LDAP groups), and allow permissions to be assigned against that group (like LDAp, but without searching)?

@atripp thx

Hi @bushman_3007, Can you clarify the request some more, i.e. why are you wanting to delete soft-deleted directories? I don't know the reason directories are soft deleted, but I suspect it has to do with preserving versioning history. Thanks, Alana

Hi @brett-polivka, We've published v2.0.1 of the Azure extension for ProGet, which should resolve this issue. You can install it from the Admin->Extensions page. Let us know if you are still having the issue after updating the extension. Thank you! -Greg

Thanks for your suggestion, @atripp, that's definitely something we'll look into when we find time to do so. In the meantime we have implemented the workaround described above, so thanks again for your help.

Also: I did remove the second website as we want ProGet to be running on the default web site on port 443 (https).

@gdivis thank you very much.

Hi @pariv_0352, I was able to fix the issue, PG-2160, and it will be released next week on ProGet 2022.2. If you would like to use the fix earlier, you can install a pre-release version of PrGet by installing ProGet 2022.0.2-CI.7 or higher. We have a walk-through on how to install prerelease products in our documentation. Please let me know if you have any questions. Thanks, Rich

Hi @gurdip-sira_1271, I did some more research on this and I think I have been able to reproduce this issue. I have created a ticket, OT-477, to track the fix for this issue. I expect to have this fixed within the next couple of versions of Otter (2022.5 or 2022.6). It is possible that this is an issue with the git extension directly, but I will update you when I have a release date for the fix. Thanks, Rich

Hi @Panda , That sounds like a great idea; I'm afraid we won't have the resources to add this in the coming weeks (we have some really cool stuff planned for BuildMaster 2022 that we're working on now). The easiest way to do local-development on the extension is to get the source code from GitHub, then build it into dll. Then, construct a new version of the Subversion.upack file with your DLL, and replace the one in the existing extensions folder. From there, restart the web/service, and your version should load instead. If you add properties to SvnRepositoryMonitor.cs that look like the other properties, they should show-up in the UI and be configurable. Let us know what you come up with, and we can definitely merge in the code and release a new version with your changes. Cheers, Alana

Hi @bbrown2_8761 , It's a bug in Visual Studio's NuGet client I'm afraid and it's not something we can realistically work-around You could post it in the NuGet issues, and they may fix it in a future version; https://github.com/NuGet/Home/issues It's really easy to reproduce, and they've definitely fixed issues like this in the past. Cheers, Alana

cool, you guys are the best! I've updated the instructions for feeds to make it copy-pasteable for users, rather than having to edit out the options/variables. Naturally I hide the originals and only show the updated ones. Example: the builtin CURL instructions for a package: To download $PackageFullName from cURL, run the following command: curl $DownloadUrl[?contentOnly=[zip|tgz]] --output $PackageName.$PackageVersion.[zip|tgz] --user <user>:<password> I simplified it to: To download $PackageFullName from cURL, run the following command: curl $DownloadUrl?contentOnly=zip --output $PackageName.$PackageVersion.zip Powershell example: To download $PackageFullName from PowerShell, run the following command: Invoke-WebRequest $DownloadUrl[?contentOnly=[zip|tgz]] -Headers @{"AUTHORIZATION"="Basic " + [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("<user>:<password>"))} -OutFile $PackageName.$PackageVersion.[zip|tgz] simplified: To download $PackageFullName from PowerShell, run the following command: Invoke-WebRequest $DownloadUrl?contentOnly=zip -OutFile $PackageName.$PackageVersion.zip

@atripp got it working without the -e, just using SQL_CONNECTION_STRING for the variable. Thanks for your help!

Hi @ehsan-bahrami91_9979 , This error message is likely related to some sort of proxy server; you can adjust proxy settings under Admin > Proxy. Cheers, Alana

I found the answer , the forwarding headers need to be added to the reverse proxy config when using linux https://docs.inedo.com/docs/https-support-on-linux server { listen 80; listen [::]:80; server_name ""; return 301 https://`$http_host`$request_uri; } server { listen 443 ssl; listen [::]:443 ssl; ssl_certificate /etc/ssl/cert/your_cert_com.crt; ssl_certificate_key /etc/ssl/cert/your_cert_com.key; server_name proget.domain.com; access_log /var/log/nginx/nginx.vhost.access.log; error_log /var/log/nginx/nginx.vhost.error.log; # Disable any limits to avoid HTTP 413 for large image uploads # ProGet requirement for VS to publish to ProGet client_max_body_size 0; # required to avoid HTTP 411: see Issue #1486 (https://github.com/dotcloud/docker/issues/1486) chunked_transfer_encoding on; location / { proxy_pass http://localhost:81; # local server proxy_http_version 1.1; proxy_cache_bypass $http_upgrade; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-Port $server_port; } }