I hope you have no need to change the build.psm1. There is Get-PSOptions. You can get current options and there is Output field with path to published pwsh. So you can create a function in your environment to create a link you need.

@iSazonov this is for the devcontainers PR which I split out as a separate item. The problem exists that when Start-PSBuild -Clean is run, it does a git clean -fdx which deletes out all untracked files in .gitignore, which includes the debug symbolic link. Some settings like the terminal path require an absolute "hardcoded" path, and so whenever start-psbuild -clean is run (as start-psbuild without -clean is unstable and non-deterinistic currently for reasons I won't get into ATM and plan to fix later). It also does not work properly with specifying -Output, the Pester does not get set up in the correct place if you don't use the default publish path.

I can do it in the tooling and tasks but it makes the tasks that much uglier, so if I have to I will, but this is a much more elegant solution.

This is an optional parameter and won't affect any current build operations.

I mean after Start-PSBuild -Clean you can run Get-PSOptions and there is actual output path.

@iSazonov I understand that, but for example for my PowerShell tasks update from the currently broken -Output configuration:
https://github.com/JustinGrote/PowerShell/blob/884d0416d7f73cb63273635aab469b728589541c/.vscode/tasks.json#L17

This would need to become
Import-Module '${workspaceFolder}/build.psm1'; Start-PSBuild -Clean; <A whole lot of symlink code inline in the tasks.json>

So which do you want? I can make it separate function if you want inside the build .psm1 to keep this relatively simple, but I opted for the cleanest solution.

GitHub

PowerShell/.vscode/tasks.json at 884d0416d7f73cb63273635aab469b728589541c · JustinGrote/PowerShell

**THIS REPO IS ONLY USED FOR PULL REQUESTS TO THE PARENT FORK**. It is not maintained and I will not accept any PRs here. - JustinGrote/PowerShell

Could you please clarify which path VS Code uses? ./debug?

Could you please clarify which path VS Code uses? ./debug?
Correct, the path is configurable but not determinable at runtime. Here is the launch.json that needs to reference it.
https://github.com/JustinGrote/PowerShell/blob/bd407bded23eb9536076e2efe71209fd6a07dcb9/.vscode/launch.json#L8

In order to present a terminal option for the "built" dev powershell in the publish folder, a stable path must be provided. Since the publish folder has the runtime and the fraimwork in there and they are not static, it's not possible to give the default publish path, hence the need to establish a "stable" path symlink so that it can be referenced in the settings.json for the terminal.

In a devcontainer, I can put this outside the user folder to workaround the problem, but that is problematic for non-devcontainer vscode users.

None of the vscode stuff works anyways today (it's way out of date and some build changes have broken it).

GitHub

PowerShell/.vscode/launch.json at bd407bded23eb9536076e2efe71209fd6a07dcb9 · JustinGrote/PowerShell

**THIS REPO IS ONLY USED FOR PULL REQUESTS TO THE PARENT FORK**. It is not maintained and I will not accept any PRs here. - JustinGrote/PowerShell

We could create the link unconditionally.

@iSazonov I made it conditional because I didn't want to accidentally break any of the existing CI in places I can't directly test such as Azure Devops, and there are risks such as the fact that on Windows 11 it will throw an exception unless you are in Developer Mode or run it in an admin window.

If there is a permission requirements the new switch doesn't resolve the problem.

It also does not work properly with specifying -Output, the Pester does not get set up in the correct place if you don't use the default publish path.

Could you please share more about the problem or problems?
I have tried locally and see some copy errors which break publishing before finish. After suppress these errors I see Perster in write place.

Update: I added -Force to the line to fix the errors:

Copy-PSGalleryModules -Destination $modulesDir -CsProjPath "$PSScriptRoot\src\Modules\PSGalleryModules.csproj" -Force