Closed ghvanderweg closed 3 years ago
thanks! We are checking this.
I think I tested this on Azure DevOps Server. Let me see if the service behaves differently.
I finally had time to test on Azure DevOps Services. It returns 100 even if you don't pass the top parameter.
It is also odd because the 100 it returns is not always the same.
To get more than 100 back you have to set the Top parameter. I think I will add a function that makes setting and clearing that easier than having to use PSDefaultParameterValues. So users with more than 100 projects are going to have to called Set-VSTeamDefaultProjectCount. I will also make it sticky like the default project so if you start a new session you don't have to call it again once you set it to a value that works for you.
It seems to me that #363 wasn't fixed in #367.
Get-VSTeamProject still only returns the first 100 projects, and only those projects are saved in the cache.
Adding
Top
to thePSDefaultParameterValues
helps with calling Get-VSTeamProject, but it doesn't increase the cache size. Trying to get a project by name that's not in the first 100 projects still fails validation.Steps to reproduce
Assuming an account with 129 projects.
Expected behavior
Actual behavior
Environment data
OS
Server