Installation of the Microsoft .NET Framework in Virtual Application Environments for Reflection Desktop

  • 7022807
  • 03-Apr-2018
  • 18-Mar-2020

Environment

Reflection Desktop (including Pro, for X, for IBM, or for UNIX and OpenVMS) 16.0 or higher
Microsoft Windows 7
Microsoft Windows 10
Microsoft Application Virtualization 5.1
Microsoft Application Virtualization 5.2

Situation

This article provides information about the Microsoft .NET Framework required by Reflection Desktop, and the recommendations for its installation in virtualization environments such as Citrix, ThinApp, App-V, Symantec, etc.

Resolution

Installation Recommendations:

Reflection Desktop requires that the Microsoft .NET Framework be installed on the PC system before it can be run.  Windows 7 and later versions already have a version of the .NET Framework pre-installed. Updates to the latest version of .NET 4.x beyond the Windows 7 defaults will be necessary for performance and security reasons.

In virtual application environments such as Citrix, ThinApp, App-V, Symantec, etc., the .NET 4 interface files required by Reflection Desktop should be OUTSIDE the virtual product package that contains Reflection Desktop.  There are a number of good reasons for this type of deployment:
  • Making the .NET Framework a part of the client-PC system, allows for a smaller virtual package for Reflection Desktop, resulting is faster download and run times.
  • Updating the .NET components is simpler.  Microsoft has issued, and will continue to issue, numerous critical security updates to the .NET components since they were first released.  If the .NET components are outside the Reflection Desktop package, they can be updated via the Windows Update process and the Reflection virtual application package does not need to be updated each time security updates are released.
  • Reflection Desktop runs faster if .NET is outside the virtual application package. There are .NET Framework components that get “pre-compiled” on the system they are run on, and thus they can be ready to go, before Reflection is started.  Significant performance improvements have been seen in some virtual application environments by having the .NET Framework outside the virtualization package.
  • During the sequencing or profiling of an application, many of the virtualization environments take a “snapshot” of the changes that occur as the product is installed.  With the complete .NET environment already installed, the snapshot taken will not need to include the .NET interface installation, leading to a cleaner deployment package.

Additional Information

Specific Virtualization Environment Recommendations:

For almost all virtual application environments, installing the complete .NET interface on the "profiling" PC before creating the virtualization package, and also installing the same .NET interface on the client PC before running the virtualization package, is sufficient.

For Citrix Environments:  When creating a streaming profile with Citrix, at the end of the Profiling steps, right-click on the Target Operating System line (like Windows 7), select Properties, and uncheck the box next to Prelaunch Analysis to prevent the package from checking for Microsoft .NET inside the package itself.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.