Skip to content
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

Closed
MaximoTrinidad opened this issue Oct 16, 2018 · 15 comments
Closed

Add PowerShell Core Architecture version to the PSVersionTable #8047

MaximoTrinidad opened this issue Oct 16, 2018 · 15 comments
Labels
Issue-Discussion the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif Resolution-No Activity Issue has had no activity for 6 months or more

Comments

@MaximoTrinidad
Copy link

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
@iSazonov
Copy link
Collaborator

You could start here.

@bergmeister
Copy link
Contributor

Do you mean the .net core runtime version by that? I would find that useful.

@iSazonov
Copy link
Collaborator

the .net core runtime version

I remember that this was rejected previously.

@vexx32
Copy link
Collaborator

vexx32 commented 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
Copy link
Author

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.

:)

@bergmeister
Copy link
Contributor

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 $PSVersionTable and the issue template

@vexx32
Copy link
Collaborator

vexx32 commented Oct 17, 2018

We can always extend the requested information beyond just $PSVersionTable

@SteveL-MSFT SteveL-MSFT added the Issue-Discussion the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif label Oct 18, 2018
@MaximoTrinidad
Copy link
Author

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
Copy link
Collaborator

Related #1635

@fMichaleczek
Copy link

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
Copy link
Collaborator

iSazonov commented May 1, 2019

@fMichaleczek We discussed this previously and rejected - the conclusion was "best practice is to test features".

Copy link
Contributor

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
Copy link
Contributor

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.

Copy link
Contributor

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 microsoft-github-policy-service bot added Resolution-No Activity Issue has had no activity for 6 months or more labels Nov 16, 2023
Copy link
Contributor

This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Discussion the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif Resolution-No Activity Issue has had no activity for 6 months or more
Projects
None yet
Development

No branches or pull requests

6 participants