In order to easily debug packages, support for launching a non-package executable inside the package container is needed. In App-V there are two methods to do this, either of which could be adopted:
- A PowerShell cmdlet like Start-AppVVirtualProcess
- A command line switch like /appvve
PowerShell would be the preferred method. We could specify the package name to identify the container to run in.
This would allow us to debug in scenarios such as:
- Launching a local PsfLauncherXX.exe with local config.json & tracefixup.dll to enable monitoring of a package without having to repackage. Similarly to test a potential fixup fixup dll prior to repackaging.
- Launching a tool like Regedit so as to see the registry the same as what the application would see.
