Repository navigation
Add PowerShell Core Architecture version to the PSVersionTable #8047
Description
I thinks it becomes necessary to include this information specially when creating a Github issue.
I want to create an RFC for this item.
Steps to reproduce
Expected behavior
Actual behavior
Environment data
> $PSVersionTable
Activity
iSazonov commentedon Oct 16, 2018
You could start here.
bergmeister commentedon Oct 16, 2018
Do you mean the .net core runtime version by that? I would find that useful.
iSazonov commentedon Oct 17, 2018
I remember that this was rejected previously.
vexx32 commentedon Oct 17, 2018
It seems to me that the request is more to do with whether PowerShell is running under x86, x64, ARM, etc., rather than the .NET core runtime version itself?
MaximoTrinidad commentedon Oct 17, 2018
Bingo! +1 Rain Sallow (/u/ta11ow) (@vexx32)
There's an existing issue where ... I don't see any issues with the 64 bit version, but seems that the 32 bit is behaving differently.
So, when creating the Github issue, the it would be nice to have identify with architecture PowerShell is running on.
:)
bergmeister commentedon Oct 17, 2018
Hmm, I can see the point but there is much more involved that can play into it such as e.g. the architecture of the OS and hardware...
We should differentiate between things that go into
$PSVersionTableand the issue templatevexx32 commentedon Oct 17, 2018
We can always extend the requested information beyond just $PSVersionTable
MaximoTrinidad commentedon Oct 18, 2018
At least... Add the session "$env:PROCESSOR_ARCHITECTURE" to the "Environment Data" section when create the issue in Github.
I think this will be helpful enough and no changes are needed to the PSTableVersion is needed.
:)
iSazonov commentedon Oct 18, 2018
Related #1635
fMichaleczek commentedon May 1, 2019
PSVersionTable between Windows x86 and Windows x64 are identical (and there are 2 differents packages)
Can we considerate adding an 'Architecture' property with $env:PROCESSOR_ARCHITECTURE value ?
iSazonov commentedon May 1, 2019
Flavien MICHALECZEK (@fMichaleczek) We discussed this previously and rejected - the conclusion was "best practice is to test features".
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 23, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.