Closed o-o00o-o closed 4 years ago
Hello!
Thanks for the feedback. I'd like to get in touch about where the priorities are for the issues you've raised. I have an email address on my profile if you'd like to get in touch.
With regards to this issue: I think this is occurring in Teste-ProjectParamsMatch
- what it is doing that it is checking that the project.params file out of the ispac and checking the contents in that match the json file provided.
I can try to suppress the output of the copyhere
if I try to do something like this from the docs:
$shell.Namespace($unpacFilepath).copyhere($item, 4)
T
UPDATE: I could use Expand-Archive.
However, and I'm loathe to say this, but I cannot replicate on my machine the flashing. I'll need to make the change then push a branch and maybe you can test for me?
Yeah great, happy to test.
Strange that it isn't happening for you. We are still running PS 5.1 due to .net framework dependencies for some of the ms sql
Also I think it will only flash if you make another application foreground while the unpack is happening
{~\S\V\Blah} [bugfixes/blah ≡] > $PSVersionTable
Name Value
---- -----
PSVersion 5.1.17763.771
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.771
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
I've removed this check as it was causing lots of problems for people as per #40
for 30 seconds or so with our package when deploying on our local machines we get a bunch of flashes where the foreground window is being taken and released creating a flashing and it means that you can't do anything else on the screen at the time
It happens during this verbose message:
Any chance this could be resolved as it is a bit antisocial 😂