Replies: 2 comments 1 reply
-
No help what so ever? Nobody knows when you get the "UNIX" version of the package? |
Beta Was this translation helpful? Give feedback.
1 reply
-
The symbolic link is
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have been building an ubuntu image installing PowerShell on it. In different ways. First I had this
But when we used this image to run a PowerShell command in our application, which is using PowerShellProcessInstance, we get an error that "-s" is an unknown cmdlet. "-s" we can see in the code is indeed automatically added. Is it because of the Powershell version we install?
I also noticed that in this case PowerShellProcessInstance.Process.StartInfo.FileName points to a "powershell.exe" not to "pwsh.exe". Setting it to "/usr/bin/pwsh" made it work (except for the -s" error).
I now created a different way of installing Powershell in our image. Using Powershell 7.4.0-preview.5.
Now the error is indeed gone. Is it because of the PowerShell version or because of the way I install it?
What I still noticed is that PowerShellProcessInstance.Process.StartInfo.FileName now points to a pwsh.exe that does not exist. I still need to set it to "/usr/bin/pwsh".
What I also noticed it that the PowerShellProcessInstance.cs files contains the compiler switch LINUX. So how does this work? When do I get the package where it was compiled with the switch defined? Is this when I actually build inside Linux and not on Windows?
Beta Was this translation helpful? Give feedback.
All reactions