VSCode extension for PowerShell Universal, anybody using it?
VSCode extension for PowerShell Universal, anybody using it?
Hi,
I used to work with VSCode and the PowerShell Universal Extension version 5.6.2.
My PSU Server meanwhile is on 2026.2.2
The old extension still somewhat works.
I can edit APP code and pages.
I can add a page.
I can restart the APP.
Same for Scripts and Apis.
Now I have tried the new extension 2026.2.2
It is all different, but ok.
The problem is that I can't edit scripts or API (Endpoints).
I can't add app pages.
And it happened that a saved some faulty code by accident, that lead to my page being still on disk, but no longer shown. I could neither delete, nor update.
All in all the new version is not usable for me so I am back to 5.6.2 which does what I need for now.
Anybody else with similar or other experience on that?
All Comments (4)
Hello deroppi,
Thank you for confirming that the behavior persists with both the PowerShell Universal server and VS Code extension on version 2026.2.2.
Your earlier report covered the inability to edit Scripts and API endpoints. This update may extend the scope to App page management, particularly when a page remains on disk but is no longer visible or manageable through the extension. We will relate these findings to the previously reported issue and verify whether the App page behavior belongs to the same problem.
Could you please provide:
* The exact error or behavior when opening a Script or API endpoint and when adding a page.
* Whether the relevant actions are missing or appear but fail.
* The sanitized relative repository path and filename of the affected page.
* How that page was originally created.
* Whether Git Sync is enabled and, if so, whether it uses One-Way or Two-Way synchronization.
Please do not manually delete the affected page yet. The appropriate recovery method depends on the repository and Git Sync configuration.
Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.
Best regards,
Ruben Tapia
I wrote that forum entry today, but it happened last week.
I meanwhile have recovered the page and switched back to the older extension.
Most pages most likely have been created through VScode with the old extension.
(I had other issues with creating pages through the web UI. The page would appear automatically in the menu, no matter what I did, and I could not remove it from being displayed. So I found, when creating via Vscode and extension I have no issues)
Git Sync is enabled, Two-Way. But I have to manually commit. Usually I control the changes and spilt into multiple commits, based on what has been changed.
The relative path for all pages is very simple. I don't use any special chars or blanks.
Typical would be a path like:
/dev/remotemtr
/common/netlookup
I will try to recreate that issue on the dev server.
I've used VS Code, the api endpoints are saved differantly on PSU it seems the extension can no longer edit them.
Hello deroppi and scheived,
Thank you both for the additional information, and please accept our apologies for the delays.
Please allow us some time to incorporate these scenarios into our lab testing this week. We will compare the behavior of resources created through VS Code and the Web UI, including the reported differences when editing endpoints and managing App pages.
We will provide an update once we have completed the initial validation.
Best regards,
Ruben Tapia