Luca

@rhuijben right, just prefix the path to the exe with the VCPKG_ROOT environment variable which has been set by the previous instance of run-vcpkg.

@rhuijben it is already installed on the runner environment: https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md#package-management

@rhuijben note that the documentation states that [`vcpkg` is preinstalled in `c:\vcpkg` on the GitHub runners](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md#package-management). If you look to the [`PATH` environment variable during a workflow run](https://github.com/lukka/CppBuildTasks-Validation/runs/5512711251?check_suite_focus=true#step:8:245), you'll see...

@rhuijben if this is still an outstanding problem let me know, we can reopen the issue. If you could also report what was the fix or the workaround, let us...

@Shatur yes, when `run-vcpkg` fails, no cache should be saved. The fix is in `v10.1`, not in `v10`. Guess the original reason was that the `v10.1` is a breaking change...

@Shatur thanks for confirming it! I knew the branches status was not correct after release of `v10.1`, but got distracted and forgot eventually about it. Totally agreed that to streamline...

FYI the only workaround is to leverage the `RUNVCPKG_NO_CACHE` environment variable. When it is set, the `run-vcpkg` post action is _not_ going to save the cache. For example, to avoid...

FYI in this PR https://github.com/lukka/run-vcpkg/pull/161 documentation is added to let user properly handle cancellation/failure in their workflow in order to not store potentially broken cached data in the GitHub cache...

as PR #161 has been completed, the documentation of how to avoid storing partial cache generated by vcpkg has been added, and this item could be closed. Let me know...

@Shatur If i get this right this is the suggestion: `run-vcpkg` could read the Git commit id from the `vcpkg.json` when - the`vcpkgGitCommitId` input is not provided. - the `vcpkg.json`...