Using Debug Tools with a Virtual Package

AdminStudio 2022 | 23.0 | Virtual Package Editor

The Virtual Package Editor lets you incorporate the following tools in a virtual package:

•

Cmd.exe (x86)—The 32-bit version of Cmd.exe on the local machine runs, and it has access to the virtual environment.

•

Cmd.exe (x64)—The 64-bit version of Cmd.exe on the local machine runs, and it has access to the virtual environment. This requires Microsoft Application Virtualization Client 4.6 or later, and it also require that the App-V package be published in a 64-bit environment.

•

Regedit.exe—Regedit.exe on the local machine runs, and it has access to the virtual environment.

These debug tools may help you troubleshoot issues in the virtual package.

Important:It is recommended that you use the debug tools only for testing. Before you release your virtual package, remove these tools from the package.

To add a debug tool to your virtual package:

1.

In the View List under Application Data, click Shortcuts.

2.

Right-click the Targets explorer, point to Add Debug Tool, and then point to the appropriate command:

•

Cmd.exe (x86)

•

Cmd.exe (x64)

•

Regedit.exe

The Virtual Package Editor adds the debug tool to the Targets explorer. The debug tool includes a shortcut that you can use to launch the tool in the virtual environment.

Adding a debug tool to a virtual package is similar to adding a target. Therefore, if appropriate, you can perform other tasks for the debug tool, just as you can for a target. For example, if you want to launch a script whenever you launch the Command Prompt window to simulate run-time behavior, you can add a script to the debug tool.

To remove a debug tool from your virtual package:

1.

In the View List under Application Data, click Shortcuts.

2.

In the Targets explorer, right-click the debug tool that you want to remove, and then click Remove.

See Also

Shortcuts View