Update how-to-determine-which-versions-are-installed.md #43947
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make script to detect old .NET Framework versions compatible with PowerShell 2
dotnet-policy-service
bot
added
the
community-contribution
|
@sdwheeler Could you take a look at this change? |
|
@gewarren I am assuming this works in PowerShell v2, but I don't have a way to test it. We don't support PowerShell v2 anymore and haven't for some time. However, the code changes are valid, and it works on the supported versions. I would say that it is safe to accept the change. |
gewarren
approved these changes
Dec 12, 2024
|
Thank you @sdwheeler @stamminator |
|
@sdwheeler If you have the Windows Powershell 2.0 option enabled in Windows Features, you can enter the v2 shell with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you're checking for old versions of .NET Framework, there's a good chance the machine is old enough to be stuck on PowerShell 2. This makes the .NET Framework version detection script compatible with PowerShell 2 and above.
Internal previews