Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

INIT task throws an exception in Windows PowerShell #65

Open
TrisBits opened this issue Dec 15, 2022 · 1 comment
Open

INIT task throws an exception in Windows PowerShell #65

TrisBits opened this issue Dec 15, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@TrisBits
Copy link

The INIT task throws an exception when called from a Windows Powershell session. This same issue was previously reported in issue #53 and fixed with merge #60. However, the fix seems to have since been reverted causing the issue to return.

Expected Behavior

PowerShellBuild tasks should also be compatible with PowerShell 5.1

Current Behavior

Receive error:
Exception: Method invocation failed because [System.IO.Path] does not contain a method named 'IsPathFullyQualified'.

Possible Solution

Re-implement the fix from merge #60

Steps to Reproduce (for bugs)

  1. Create a new module with Stucco
  2. Execute .\build.ps1 from a Windows PowerShell terminal

Context

I was attempting to build a PowerShell 5.1 module. Once I modified the Initialize-PSBuild function based on the change in merge #60 it worked flawlessly.

Your Environment

*Module version used: 0.6.1
Operating System and PowerShell version: Windows 10 with PowerShell 5.1
Running .\build.ps1 from the Stucco template

@meterien
Copy link

I can reproduce this on my end too, but work in Powershell 7.3.2

@devblackops devblackops added the bug Something isn't working label Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants