For App-V Clients running on Windows XP, the App-V 4.5 Client and above will support the virtualization of the .NET 2.0 Framework. This is documented here:
However, there is an additional step that must be taken during the monitoring phase after the .NET 2.0 installations has completed and before monitoring is stopped.
At the end of installing .NET during the monitoring phase, you will need to do a manual file copy of a directory due to the fact that a critical directory is created and referenced as a symlink (symbolic link.)
To rectify this, all of the files in the directory:
will need to be copied by hand to this directory:
Simply open a command prompt and type in the command:
XCOPY %windows%\winsxs\x86_System.EnterpriseServices_b03f5f7f11d50a3a_126.96.36.199_x-ww_7d5f3790 %windows%\assembly\GAC_32\System.EnterpriseServices\188.8.131.52__b03f5f7f11d50a3a /s /e
If the sequence of .NET used the %SFT_MNT% of Q:\DotNet then this would copy the files in
Q:\DotNet\VFS\CSIDL_WINDOWS\winsxs\x86_System.EnterpriseServices_b03f5f7f11d50a3a_184.108.40.206_x-ww_7d5f3790 to the directory located at
If you already have sequenced .NET 2.0 and need to correct this you can fix this by performing the following steps:
1. Open the existing package for upgrade.
2. Begin monitoring.
3. Launch a Command Prompt.
4. Simply open a command prompt and type in the command:
5. Stop monitoring and save the package.
The new package will now have the correct files under: