peppekerstens

I'll be posting a PR soon with fixes :)

My reasoning for these changes; - 'BUILD_SOURCEVERSIONMESSAGE' was already in version 2.0.9. - 'SYSTEM_WORKINGDIRECTORY' was already pointing to an path, 'AGENT_RELEASEDIRECTORY' is pointing to same path. - I could not...

@FISHMANPET one last thing; in another issue you argument that this module is/can be used in different ways. (in your case it was a PS script, not a module if...

We're getting somewhere :) Yes, they are always populated. But in my particular case I want them ignored. Especially when I start a release; then i gather A LOT OF...

yup; saw it too. wrong typecasted. silly me do not agree with GBVParams though; every function has it's own (but same!) default behavior for detection path. ```powershell param( $Path =...

@PlagueHO: Agree. Primary key for this resource should be the interface alias. Same as the command being used (Set-DnsClient). Not one of its settable properties (which is currently so).

In addition to @jborean93: use [Nuget explorer](https://github.com/NuGetPackageExplorer/NuGetPackageExplorer) [NUGet explorer](https://www.microsoft.com/nl-nl/p/nuget-package-explorer/9wzdncrdmdm3?ocid=badge&rtc=1&activetab=pivot:overviewtab) or equivalent RHEL GUI tool to validate your nuget source. Also, check if NuGet is present as a provider in PowerShell...

confirmed. based on this code example: ```powershell get-azsubscription | where name -like '*somename*' |select-azsubscription $vault = Get-AzRecoveryServicesVault$currvault = $vault | where Name -like '*blah*' $BackupItemList = Get-AzRecoveryServicesBackupItem -vaultId $currvault.ID -BackupManagementType...

@nzalex1 as stated above, as a workaround, try AZ 9.3.0, or more specific; az.RecoveryServices 6.1.2

I've made a proxy function for Out-Gridview to include Out-ConsoleGridview. Maybe include it in this module as a work-around in meantime? https://gist.github.com/peppekerstens/b6553910fa316cfe9bdab2d73a3476a5