alerickson
alerickson
Thanks @keystroke! Could you try running `Install-Module -Name AzureStack -Repository azrc -RequiredVersion 2.0.0-preview -AllowPrerelease -Scope CurrentUser` in PowerShell Core as well?
I noticed that the issue occurred to modules that have Az.Accounts as a dependency. Whenever the Az.Accounts module was being used by the process but also being checked by PowerShellGet...
I also wasn't able to repro this
@chreestopher I think I know what the issue was here. If you run `Get-Module PowerShellGet, PackageManagement -ListAvailable` you get a list of all of the versions that exist on your...
@alexbuzzbee has this been happening with different versions of PowerShellGet? Do you have the System.Management.Automation .dll on your machine?
@alexvergilis @alexbuzzbee could you both let me know which dlls you have loaded when you're encountering this issue ([System.AppDomain]::CurrentDomain.GetAssemblies())
@Nevember thanks for the detailed repro information! Were you able to try the repro with 3.0.17-beta17 in Windows 10 and Windows 11?
Thanks for pin-pointing the problem! From your original post it seems like the nupkg is getting created properly but somehow parsing the full file name isn't working. Could you let...
@KevinZonda thank you! That's unfortunate, from the logs it seemed like the .nupkg was getting created properly, but not pushed (possibly due to incorrect parsing), but I'll have to dig...
Getting out a PackageMangement release today that will fix this!