Skip to content

Conversation

@SteveL-MSFT
Copy link
Member

The ClrVersion property of $PSVersionTable is not useful with CoreCLR and end users should not be using
that value to determine compatibility. Recommendation from dotnet team is to remove that property.

Fix #1395

… end users should not be using

that value to determine compatibility.  Recommendation from dotnet team is to remove that property.
@SteveL-MSFT SteveL-MSFT requested a review from iSazonov June 15, 2017 22:48
@lzybkr lzybkr added the Breaking-Change breaking change that may affect users label Jun 16, 2017
Copy link
Collaborator

@iSazonov iSazonov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SteveL-MSFT
Copy link
Member Author

@iSazonov will remove those

@iSazonov
Copy link
Collaborator

LGTM.

@SteveL-MSFT
Copy link
Member Author

@mirichmo can you merge?

}
}

internal static Version CLRVersion
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is our stance on removing FullCLR compatibility of the code? If we are dropping that requirement and only focusing on CoreCLR, then you should remove PSCLRVersionName from line 77 as well.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed it since we removed the other members anyways. After beta.3 goes out, I intend to revisit the discussion about removing FullCLR code.

@mirichmo mirichmo merged commit a66cd0b into PowerShell:master Jun 19, 2017
@SteveL-MSFT SteveL-MSFT deleted the clrversion branch June 28, 2017 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Breaking-Change breaking change that may affect users

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants