Skip to content

Improve check for developer mode by checking minimum required build number - #8749

Merged
Travis Plunk (TravisEz13) merged 5 commits into
PowerShell:masterfrom
adityapatwardhan:FixSymLinkTest
Jan 25, 2019
Merged

Improve check for developer mode by checking minimum required build number#8749
Travis Plunk (TravisEz13) merged 5 commits into
PowerShell:masterfrom
adityapatwardhan:FixSymLinkTest

Conversation

@adityapatwardhan

@adityapatwardhan Aditya Patwardhan (adityapatwardhan) commented Jan 25, 2019

Copy link
Copy Markdown
Member

PR Summary

The test would fail if the developer mode is enabled but the machine has an older build than the minimum required build.
The change adds a check for the build version in the test.

PR Context

The current is causing CI failures.

PR Checklist

…umber

The test would fail if the developer mode is enabled but the machine has an older build than the minimum required build.
The change adds a check for the build version in the test.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

this isn't blocking, but it might be easier to read/maintain

Comment thread test/powershell/Modules/Microsoft.PowerShell.Management/New-Item.Tests.ps1 Outdated
Comment thread src/System.Management.Automation/namespaces/FileSystemProvider.cs Outdated
@TravisEz13

Copy link
Copy Markdown
Member

merging this because it is blocking PRs.

@TravisEz13
Travis Plunk (TravisEz13) merged commit 6ccbebd into PowerShell:master Jan 25, 2019
@iSazonov Ilya (iSazonov) added the CL-Engine Indicates that a PR should be marked as an engine change in the Change Log label Feb 1, 2019
@powercode

Copy link
Copy Markdown
Collaborator

Aditya Patwardhan (@adityapatwardhan) I'm a bit late to the party here, but I noticed that we are depending a manifest in the binary for OSVersion to give correct results. This doesn't seem to happen when we run the tests, as they are loaded into the dotnet.exe binary. I get version 6.2 on my windows 10 machine when running the tests.

@SteveL-MSFT

Copy link
Copy Markdown
Member

Staffan Gustafsson (@powercode) Windows API, by default, will return 6.2 for the Windows Version. For Windows PowerShell and PowerShell Core, we rely on a compatibility section in the app manifest to have it return 10. If you're referring to unit tests running in dotnet.exe, it may be ok to expect 6.2 as long as it's understood.

@powercode

Copy link
Copy Markdown
Collaborator

Steve Lee (@SteveL-MSFT) It's just annoying when the tests don't behave as the product.
Maybe the right thing to do to get dotnet.exe to have a manifest too.

Thatgfsj (Thatgfsj) pushed a commit to Thatgfsj/PowerShell that referenced this pull request Aug 6, 2026
…umber (PowerShell#8749)

* Improve check for developer mode by checking minimum required build number

The test would fail if the developer mode is enabled but the machine has an older build than the minimum required build.
The change adds a check for the build version in the test.

* Update test/powershell/Modules/Microsoft.PowerShell.Management/New-Item.Tests.ps1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-Engine Indicates that a PR should be marked as an engine change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants