@caesay Is there any reason why this is not merged yet?

We are not sure that this is the correct approach, as this would be the first time the publisher field is used in application path's. It requires further consideration before we can move forward with this approach or possibly with some alternative like a package namespace.

Understand, but correct me if I am wrong but then the documentation is wrong?

The documentation is why I submitted this as I was testing PerMachine installs and was not getting the install location stated in the documentation

Why not add an option to vpk pack to set a custom default PerMachine path?

And while we're on the subject, it would also be great if there were an additional option for vpk pack that enables the installation user to select the installation path during the setup process for PerMachine installations.

What do you think?