-
Notifications
You must be signed in to change notification settings - Fork 7.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add PowerShell Core Architecture version to the PSVersionTable #8047
Comments
You could start here. |
Do you mean the .net core runtime version by that? I would find that useful. |
I remember that this was rejected previously. |
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? |
Bingo! +1 @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. :) |
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 can always extend the requested information beyond just $PSVersionTable |
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. :) |
Related #1635 |
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 ? |
@fMichaleczek We discussed this previously and rejected - the conclusion was "best practice is to test features". |
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. |
2 similar comments
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. |
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. |
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes. |
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
The text was updated successfully, but these errors were encountered: