PowerShell5 breaks EntityFramework install?

[rrelyea]

Please investigate this issue that came via internal email.

[divega]

@zhili1208 @rrelyea can you share more information about this?

[zhili1208]

@divega this issue only repro on customer's win7 machine, doesn't repro on customer's win10. Also I didn't get an repro on my win7 box. The problem is that the ps1 files literally does not exist when PowerShell tries to run it. It is created and the contents written to it just milliseconds later.

[divega]

Thanks @zhili1208. Do you mean the ps1 file from the package hasn't been written to disk?

cc @bricelam and @natemcmaster for insights or in case they have seen anything like this.

[natemcmaster]

The problem is that the ps1 files literally does not exist when PowerShell tries to run it. It is created and the contents written to it just milliseconds later.

EF Core commands has two different ps1 files, tools/init.ps1 and tools/install.ps1. Does NuGet ensure extraction from nupkg is complete before executing init.ps1 and/or install.ps1?

[zhili1208]

@natemcmaster Yes, I think nuget ensure the extraction complete, I will ask customer to verify this again, will provide more info later.

[zhili1208]

@divega @natemcmaster the customer found the root problem, when they removed a policy that prevented powershell scripts from running, they still had an __PSLockDownPolicy environment variable set to 4, which after removal, appears to have corrected the issue.

[divega]

Glad to hear. Thanks!

[bricelam]

Can NuGet warn during package install if that's set?

[zhili1208]

@bricelam Yes, I think Nuget did some policy check even change policy for customer before, I will check that, if there is no that check, will file an bug for that.