Specifying the Diagnostic Tools to Include With the App-V Package

AdminStudio 2021 | 21.0 | Automated Application Converter

You can choose to include the following diagnostic tools with your App-V package:

•

Launcher Tool—The App-V Package Launcher can be used to quickly publish the App-V package to the local machine for testing. This tool is available for both App-V 4.x and 5.x packages. You can use the App-V package Launcher to test a newly built App-V package before moving it to a deployment server.

•

File System Diagnostic—The Windows Command Prompt tool enables you to look at the file system for the application while it is running in its virtual environment. You can use it to investigate the file system and launch other tools within the virtual environment context. This tool is only available for App-V 4.x packages.

•

Registry System Diagnostic—The Registry Editor tool enables you to look at the registry for the application while it is running in its virtual environment. This tool is only available for App-V 4.x packages.

You can use the App-V Package Launcher to test a newly built App-V package before moving it to a deployment server. And if, during testing, you received an error message stating that the application cannot load a DLL, you could use the File System Diagnostic and Registry System Diagnostic tools to troubleshoot the problem.

Tip:Because the App-V 5.x Application Launcher has a built-in Windows Command Prompt tool, it is not necessary to include the File System Diagnostic or Registry System Diagnostic tools with App-V 5.x packages.

To specify which diagnostic tools to include with an App-V package, perform the following steps:

To specify the diagnostic tools to include with an App-V package:

1.

On the Packages tab, select the package you want to edit. Package properties are displayed in the Properties window.

2.

In the Properties window, under Microsoft App-V Options (All Versions), set the Launcher Tool property to one of the following values:

•

Enabled—Include the App-V Package Launcher when you build an App-V package.

•

Disabled—Do not include the App-V Application Launcher when you build an App-V package.

•

Default—Use the setting on the Project Options dialog box.

3.

In the Properties window, under Microsoft App-V Options (Version 4.x), set the File System Diagnostic property to one of the following values:

•

Enabled—Include the Windows Command Prompt application with your App-V package so that you can browse the virtual file system at runtime from within the virtual environment. If this option is selected, a file named Virtual File System.osd will be created in the App-V Package folder, which can be used to display the files and folders within the virtual environment. You can use Virtual File System.osd to view the existing files and folders on the computer plus the files and folders for the virtual package. A shortcut to the command prompt will be added to the App-V package.

•

Disabled—Do not include the Windows Command Prompt application with your App-V package.

•

Default—Use the setting on the Project Options dialog box.

4.

In the Properties window, under Microsoft App-V Options (Version 4.x), set the Registry System Diagnostic property to one of the following values:

•

Enabled—Include the Registry Editor (regedit.exe) with your App-V package so that you can browse the registry at runtime from within the virtual environment. If this option is selected, a file named Virtual Registry.osd will be created in the App-V Package folder, which can be used to display the registry within the virtual environment. You can use Virtual Registry.osd to view the existing registry on the computer plus the registry for the virtual package. A shortcut to the registry option will be added to the App-V package.

•

Disabled—Do not include the Registry Editor (regedit.exe) application with your App-V package.

•

Default—Use the setting on the Project Options dialog box.

See Also

Packages Tab

Project Options Dialog Box