Justin Grote

Thanks for the report! Have you tried the preview version of the extension and see if it is still an issue there?

I wrote the dynamic IB generator for PSAke tasks so probably missed an edge case with the latest update, I'll take a look! On Tue, Dec 18, 2018, 3:39 AM...

Sorry for the delay. So the way the new script works is proxying the psake statement such as Task with "Convert-Task", which then parses the psake statement and spits out...

If we go manual, probably the best way is to apply Pester tests to both task types to ensure the same output result. Short of someone helping, this is totally...

I'd say manual as well since I haven't had time to dedicate to fixing the wrapper. If I do then it will detect if a task has been manually written...

See the PR. After fixing that or adding this to your invoke-build file header: ```powershell if (-not (Get-Module PowershellBuild)) {Import-Module PowershellBuild} . PowerShellBuild.IB.Tasks $PSBPreference.Build.CompileModule = $true task Build $psbpreference.build.dependencies task...

@devblackops doesn't generate an artifact as part of the appveryor build so I can't check for sure, let me try compiling it locally. Is the problem that the assert doesn't...

Ah I see. Since it's not part of the original psake task, it wouldn't incorporate your change, because the file gets dynamically generated at build time. It would need to...

Also if you're interested in Native IB tasks, check out my PowerCD module, though I'm working to abstract them into functions so they can be included here because I believe...

It can always be both, we can modify the script to do automatic ones as a separate file and then have the manual ones as another one, that way they...