Trying to get the extension working connecting to our production instance which runs on a server using IIS.
I’m able to connect, refresh, open log files, etc. But anytime i try to open or edit any of the ps1 scripts i revieve the following error…
Error running command powershell-universal.openConfigFile: ENOENT: no such file or directory, open ‘c:\PowerShellUniversalServer\UniversalAutomation\Repository.universal\roles.ps1’. This is likely caused by the extension that contributes powershell-universal.openConfigFile.
It’s looking to open the file from my local “c:” instead of the servers root. I’ve set the path to the remote server executable in the settings using the FQDN and path and also mapping the drive locally to my workstation and using “Q:\PowerShellUniversalServer”… but no matter what i change it to it still looks to local “C:” for the file. Is there some setting i’m missing???