Christian Sandfeld

What really puzzled me was that even when running ```nuget.exe``` manually, trying to get ```TestMod99``` downloaded, it would still complain about ```psdepend``` in the message. I even tried moving ```nuget.exe```...

**build_psdepend.ps1:** ```PowerShell $tempPath = Join-Path -Path $PSScriptRoot -ChildPath 'temp' $tempModulePath = Join-Path -Path $tempPath -ChildPath 'modules' $installPSDependPath = Join-Path -Path (Join-Path -Path (Join-Path -Path $PSScriptRoot -ChildPath 'build') -ChildPath 'helpers') -ChildPath...

I agree - changing the current default behavior would come with a high risk of messing it up for existing deployments depending on tags. A `-TagOperator` parameter or something similar...

Yup - using namespaced names works - thank you for your speedy reply

On another note ... is there a way to setup a task, to only run if specific tasks are used? In other words, if Invoke-PSDeploy is invoked without specifying the...

No worries, and sorry for the late reply. Racking my brain to try and remember what that was all about, but comming up short.

@fflaten while it may be by design, from a user perspective I would expect names to always be expanded no matter what state the test ends up in.

I am sure there are good reasons for the current implementation, but I did notice that when skipping tests using Set-ItResult like this ```PowerShell $sb = { Describe 'Test names...

Thank you for the insights @nohwnd, appreciate you taking the time to explain.

Interesting find @GitHubEddie. I had a look at the AST for each "type" of scriptblock, and I guess the problem is caused by missing data in the AST `Parent` property...