How to Sequence Visual Studio 2010 in Microsoft Application Virtualization

InformationThis article describes one method that you can use to sequence Microsoft Visual Studio 2010 for use with Microsoft Application Virtualization (App-V). The method that is described in this article is not the only possible method. Additionally, you may have to adapt the information in this article as appropriate for your particular environment.

Application Name: Visual Studio 2010

Application Version: Service Pack 1

Company Name: Microsoft Corporation

Sequencer Version: App-V 4.6 SP1

App-V Client Version Tested On: App-V 4.6 SP1

Operating System Sequenced On: Windows XP SP3; Windows Vista; Windows 7 SP1; Windows Server 2003 R2 SP2; Windows Server 2008 SP2; Windows Server 2008 R2 SP1

Pre-requisites:

You must have the following to sequence Visual Studio 2010 for use with Microsoft Application Virtualization:

· A volume license for Visual Studio 2010

· Visual Studio 2010 Service Pack 1 or a later version

· Hotfix 2526163 for Visual Studio 2010 Service Pack 1

· Microsoft Application Virtualization 4.6 SP1 or a later version

· Microsoft .NET Framework 4 Full Profile natively installed on the App-V Sequencer and App-V Clients to which the sequencing will be deployed.

· If you are using Windows 7 or Windows Server 2008 R2, you must use Windows 7 SP1 or Windows Server 2008 R2 SP1 or later on the App-V Sequencer and App-V Clients.

Client Operating Systems Successfully Deployed To: Windows XP SP3; Windows Vista; Windows 7 SP1; Windows Server 2003 R2 SP2; Windows Server 2008 SP2; Windows Server 2008 R2 SP1

Posted by Microsoft Employee: Jim Boyles

Corresponding KB Article Reference:

For Visual Studio 2010 Service Pack 1, you have to obtain Hotfix 2526163. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2526163 FIX: Error message when you try to start a sequenced Visual Studio 2010 application package on an Application Virtualization client: "Invalid license data. Reinstall is required"

Steps to Sequence the Application

Background

Obtain Background Information

· Review the Microsoft Application Virtualization 4.6 SP1 Sequencing Guide white paper available on TechNet.

· Install Visual Studio 2010 to become familiar with the functionality of the program.

Prepare the Environment

Make sure that you allocate at least 3 gigabytes (GB) of random access memory (RAM) to the computer on which you will sequence Visual Studio.

Sequence Visual Studio 2010

Note: Please complete all sequencing steps logged in as a local administrator.

1. Install Microsoft .NET Framework 4 Full Profile on the Sequencer machine. Using Microsoft Update, install all updates for Windows and .NET Framework.

2. Make sure that the following update was installed by Microsoft Update on the Sequencer machine. If not, install it manually. 2468871 Update for the .NET Framework 4

3. On the Tools menu, click Options. Click on the Exclusion Items tab.

4. Add the following exclusions:

Exclude Path

Mapping Type

%CSIDL_WINDOWS%\Assembly\NativeImages_v4.0.30319_32

VFS

%CSIDL_WINDOWS%\Assembly\NativeImages_v4.0.30319_64

VFS

%CSIDL_WINDOWS%\Assembly\NativeImages_v2.0.50727_32

VFS

%CSIDL_WINDOWS%\Assembly\NativeImages_v2.0.50727_64

VFS

\Registry\Machine\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\NGENService\Roots

VRG

\Registry\Machine\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727\NGENService\Roots

VRG

\REGISTRY\MACHINE\Software\Microsoft\Fusion

VRG

For Windows XP and Windows Server 2003, also add the following exclusions:

Exclude Path

Mapping Type

%CSIDL_WINDOWS%\Microsoft.Net\assembly\GAC_32\System.EnterpriseServices

VFS

%CSIDL_WINDOWS%\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices

VFS

5. On the File menu, click Save As Template… to save these exclusions as a project template.

6. On the File menu, click New From Template… to start sequencing using the newly created template.

7. Complete the initial pages of the New Package Wizard.

8. Start monitoring the installation.

9. Install Visual Studio 2010. Use the default options, except for the following:

a. Be sure to specify the install location as Q:\VS2010.

b. Install everything except Microsoft SharePoint Developer Tools and SQL Server 2008 Express.

10. On 64-bit systems (x64), open regedit and create the following keys after Visual Studio 2010 installation completes:

a. HKLM\SOFTWARE\MICROSOFT\PLAYREADY

b. HKLM\SOFTWARE\WOW6432NODE\MICROSOFT\PLAYREADY

11. Install Visual Studio 2010 Service Pack 1

12. Install Hotfix 2526163 for Install Visual Studio 2010 Service Pack 1

a. Launch an elevated Visual Studio 2010 Command prompt while monitoring. Note: You do not need to run elevated on Windows XP or Windows Server 2003.

b. Run DDConfigCA.exe from the command prompt.

c. Exit the command prompt.

13. After installation completes, run the following from an elevated command prompt: %WINDIR%\Microsoft.NET\Framework\v4.0.30319\ngen executeQueuedItems

14. On 64-bit systems (x64), also run the following from an elevated command prompt: %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\ngen executeQueuedItems

15. Launch an elevated Visual Studio 2010 Command prompt. Note: You do not need to run elevated on Windows XP or Windows Server 2003. Execute the command:

a. On 32-bit systems (x86): gacutil /i “%ProgramFiles%\Microsoft Silverlight\4.0.50826.0\System.Windows.dll”

b. On 64-bit systems (x64): gacutil /i “%ProgramFiles(x86)%\Microsoft Silverlight\4.0.50826.0\System.Windows.dll”

16. If you are sequencing Visual Studio 2010 Ultimate, modify intellitrace.exe.config. Modify the startup xml node to add an attribute useLegacyV2RuntimeActivationPolicy : <startup useLegacyV2RuntimeActivationPolicy="true"> in the following 2 locations:

a. Q:\VS2010\Common7\IDE\PrivateAssemblies\DataCollectors

b. Q:\VS2010\Team Tools\TraceDebugger Tools

17. For64-bit systems (x64), perform the following steps:

a. Open the registry key HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\App Paths\Iexplore.exe.

b. Modify the Default value of this key to place quotes around the path. For example, if the current value is C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE,change the value to “C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE” .

c. Modify the Path value of this key to place quotes around the path. For example, if the current value is C:\Program Files (x86)\Internet Explorer, change the value to “C:\Program Files (x86)\Internet Explorer” .

18. Stop monitoring the installation.

19. Continue to the customization page

20. On the Toolsmenu, click Diagnostics | Command Window.

a. Run regedit.

b. Delete the value HKLM\Software\Microsoft\VisualStudio\10\SetupCommandLine

c. Exit regedit and the command prompt.

21. Go to the VFS tab on the Sequencer. Delete all files named webengine4.dll. If no files are found with the specified name, skip this step.

22. On the OSD tab, add the following environment variable to all the OSDs:

a. On 32-bit systems (x86):PATH=%PATH%;%WINDIR%\Microsoft.NET\Framework\v4.0.30319

b. On 64-bit systems (x64): PATH=%PATH%;%WINDIR%\Microsoft.NET\Framework64\v4.0.30319;%WINDIR%\Microsoft.NET\Framework\v4.0.30319

23. Save the package.

On the App-V Client

Be sure to complete the following steps on all App-V Clients to which the sequencing will be deployed.

1. Install Microsoft .NET Framework 4 Full Profile. Using Microsoft Update, install all updates for Windows and .NET Framework.

2. Make sure that the following update was installed by Microsoft Update. If not, install it manually. 2468871 Update for the .NET Framework 4

3. Run services.msc and disable the Windows Presentation Foundation Font Cache service.

=====

The above text was originally published by Jim Boyles here:

https://social.technet.microsoft.com/Forums/en-US/prescriptiveguidance/thread/5eade6a1-44b1-41f9-8af2-0534ef5c8c71

J.C. Hornbeck | System Center Knowledge Engineer

App-V Team blog: https://blogs.technet.com/appv/
AVIcode Team blog: https://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: https://blogs.technet.com/configurationmgr/
DPM Team blog: https://blogs.technet.com/dpm/
MED-V Team blog: https://blogs.technet.com/medv/
OOB Support Team blog: https://blogs.technet.com/oob/
Opalis Team blog: https://blogs.technet.com/opalis
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: https://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: https://blogs.technet.com/mdm/
SCVMM Team blog: https://blogs.technet.com/scvmm
Server App-V Team blog: https://blogs.technet.com/b/serverappv
Service Manager Team blog: https://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: https://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: https://blogs.technet.com/sus/

clip_image001 clip_image002