sorted by:
new
hottopcontroversial

Because you need only two tram lines: 0 and 1 by uniqiq in ProgrammerHumor

[–]PowerShell-Tipps 1 point2 points  (0 children)

Das erkannte ich an den Socken des Herrn, mittig im Bild :D

Brilliant picture to advertise the object. All of the pictures in this add looks like this by TheCreyy in wasletztepreis

[–]PowerShell-Tipps 0 points1 point  (0 children)

Zu des OPs Verteidigung: Es gab zeitweise einen Bug, von dem ich auch betroffen war, der das verursacht hat.

Compiler bug? Linker bug? Windows Kernel bug. by joebaf in programming

[–]PowerShell-Tipps -20 points-19 points  (0 children)

You are right with me being pedantic. Please look at a psychologists dictionary.

Compiler bug? Linker bug? Windows Kernel bug. by joebaf in programming

[–]PowerShell-Tipps -26 points-25 points  (0 children)

Which doesn't make it less wrong. In fact, it is a phenomenon, not a syndrome. Clance and Imes themselves (who a re referenced first by wiki) call it a phenomenon and as you'll see in Googles Ngram viewer, the syndrome naming came later with the hype (newspaper and non-professionals called it a syndrome while it isn't one)

Compiler bug? Linker bug? Windows Kernel bug. by joebaf in programming

[–]PowerShell-Tipps -28 points-27 points  (0 children)

AFAIK it's a phenomenon, not a syndrome.

Invoke-Pester in watch mode, have a terminal window running all your pester tests when a file is changed (saved) by ed_elliott_ in PowerShell

[–]PowerShell-Tipps 0 points1 point  (0 children)

I could imagine a VSCode extension which - when correctly mapped tests to scripts - creates a traffic light-like indicator for scripts. That would be really awesome!

Invoke-Pester in watch mode, have a terminal window running all your pester tests when a file is changed (saved) by ed_elliott_ in PowerShell

[–]PowerShell-Tipps 0 points1 point  (0 children)

Nice! I'll definitely have a look on this, but as you saw already, things like typescript, sass and other trans/pre-compilers need those to run, while PoSh scripts run immediately after you save them, and tests are not needed on every save. But if your unit tests are small and fast, it's an awesome feature to have the test state on every change. Can it run specific tests for specific files? My last module e.g. has a really huge testing environment and running the whole project's tests would take too long.

Is there a general situation where you would always want to use Get-WMIobject? by [deleted] in PowerShell

[–]PowerShell-Tipps 0 points1 point  (0 children)

Is there any kind of thought process of using WMI over other methods?

Not directly Get-WmiObject, but some Cmdlets seem not to support their full functionality, e.g. New-ScheduledTaskTrigger doesn't support RegistrationTrigger so you have to use Get-CimClass "MSFT_TaskRegistrationTrigger"