| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
… end users should not be using that value to determine compatibility. Recommendation from dotnet team is to remove that property.
There was a problem hiding this comment.
I believe we should remove internal static Version CLRVersion and internal const string PSCLRVersionName
Sorry, something went wrong.
|
Ilya (@iSazonov) will remove those |
Sorry, something went wrong.
|
LGTM. |
Sorry, something went wrong.
|
Mike Richmond (@mirichmo) can you merge? |
Sorry, something went wrong.
| } | ||
| } | ||
|
|
||
| internal static Version CLRVersion |
There was a problem hiding this comment.
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.
Sorry, something went wrong.
There was a problem hiding this comment.
Removed it since we removed the other members anyways. After beta.3 goes out, I intend to revisit the discussion about removing FullCLR code.
Sorry, something went wrong.
* ClrVersion property of $PSVersionTable is not useful with CoreCLR and end users should not be using it that value to determine compatibility. Recommendation from dotnet team is to remove that property. * Removed internal members used for CLRVersion * removed CLRVersion from FullCLR build as well * added additional information to run `start-psbootstrap -buildnative` if cmake is not found
| Back | FazBrowse Home | New Git URL |
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