Archive

Posts Tagged ‘visualstudio’

App-V: Error Message when trying to launch a Virtualized Instance of Visual Studio 2010

January 16, 2012 Leave a comment

Microsoft App-V is the only application virtualization product capable of virtualizing Visual Studio 2010. However, you may receive the following error message when attempting to launch the primary development environment (DEVENV.EXE) within a Visual Studio 2010 package virtualized with Microsoft App-V:

The ‘Environment Package Window Management’ package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by running the application together with the /log parameter on the command line, and then examining the file ‘C:users<USERNAME>AppDataRoamingMicrosoftVisualStudio10.0ActivityLog.xml’.

Continue to show this error message?

 This is nothing to be alramed about. This can happen if one or more of the following is missing/configured incorrectly on the App-V Client where the Visual Studio package is being deployed:

– The Microsoft .NET Framework 4 Full Profile
– The KB 2468871 Update
– Interference from the Windows Presentation Foundation Font Cache Service.

 

To resolve this issue, be sure to complete the following steps on all App-V Clients to which the virtualized package of Visual Studio 2010 will be deployed.

1. Install Microsoft .NET Framework 4 Full Profile.  Using Microsoft Update, install all updates for Windows and .NET Framework.  The full download for the .NET Framework 4 Full Profile can be found here:

http://www.microsoft.com/download/en/details.aspx?id=17718

2. Make sure that the following update was installed by Microsoft Update.  If not, install it manually from the following location: http://www.microsoft.com/download/en/details.aspx?id=3556

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

 

A Visual Studio 2008 Package Sequenced with Microsoft Application Virtualization may not Function Properly after Upgrading to Visual Studio Service Pack 1

October 18, 2011 Leave a comment

Symptoms:

If you open a Visual Studio 2008 package for upgrade (or simply upgrade in the 4.6 SP1 sequencer) and upgrade the package to Visual Studio Service pack 1, it may fail to function properly on the App-V Client.

Cause:

This is caused by the Visual Studio SP1 installer setting a reparse point for key SxS (side-by-side) assemblies. The Visual Studio  2008 Service Pack 1 installer sets a reparse point from

<%SFT_MNT%><root>VFSCSIDL_WINDOWSassemblyGAC_MSILWcfSvcHost.0.0.0__31bf3856ad364e35

to

<%SFT_MNT%><root>VFSCSIDL_WINDOWSWinSxSMSIL_WcfSvcHost_31bf3856ad364e35_9.0.0.0_x-ww_e0abf5ea

This means that if the application on the client looks for the files in the first location, they won’t be found because they are actually only located in the latter.  When running virtualized on the client, the VFS does not reflect to the application the fact this is a reparse point. The application thinks the files will be located here but they are not actually found here.

Resolution

During the monitor phase, when the upgrade application has completed, you will need to open a  command prompt and copy the files from:

Q:<root>VFSCSIDL_WINDOWSWinSxSMSIL_WcfSvcHost_31bf3856ad364e35_9.0.0.0_x-ww_e0abf5ea

to

Q:<root>VFSCSIDL_WINDOWSassemblyGAC_MSILWcfSvcHost.0.0.0__31bf3856ad364e35

so they are located in both locations.

For example, If the drive used for the SFT_MNT volume is Q:, then the syntax for copying via XCOPY would be:

XCOPY /S /E Q:<root>VFSCSIDL_WINDOWSWinSxSMSIL_WcfSvcHost_31bf3856ad364e35_9.0.0.0_x-ww_e0abf5ea Q:<root>VFSCSIDL_WINDOWSassemblyGAC_MSILWcfSvcHost.0.0.0__31bf3856ad364e35

Categories: Uncategorized Tags: , , , ,

Important notice for those of you building C++ projects with App-V virtualized Visual Studio 2008 . . .

March 31, 2011 1 comment

. . . if you build it with debugging enabled it will not complete and will throw an error in the console window.

When using a virtualized instance of Visual Studio (sequenced following the instructions at http://technet.microsoft.com/en-us/appvirtualization/dd334515.aspx)

When users build a C++ project in Visual Studio 2008 with debugging enabled the compiled program will not run and gives an error in the console window and/or the interface.

ERROR in Visual Studio Interface:

 “Unable to start program ‘path_to_program\program_name.exe’.”

“This application has failed to start because the application configuration is incorrect. Review the manifest file for possible errors. Reinstalling the application may fix this problem. For more details, please see the application event log.”

ERROR in console window:

“The system cannot execute the specified program.”

[To reproduce this specifically:

Create a new empty C++ project in Visual Studio. Write any compilable and runable code. Build the project (F7). Run the project without debugging (CTRL+F5) ]

 This problem does not occur when the project is set to release mode – only in debug mode.

This is caused by the debug run-time modules not being captured inside the virtual application package because of how the Application Virtualization side-by-side process works during sequencing. The debug runtimes are not used, so they are left out.

In order to work around this, the developer will need to install the debug runtimes on the local machine. They can be built out of Visual Studio 2008 pretty easily as follows:

 1. From Visual Studio, navigate to “File” – “New” – “Project.”

2. Select and expand “Other Project Types,” then “Setup and Deployment.”

3. In the Visual Studio Templates area, select “Setup Project.” Click “OK.”

4. In the Project window, Right-click “Setup1” and select “Add” – “Merge Module.”

5. Select all debug runtimes desired from the list.

6. Click Open

7. Right-click Setup1 and select “Build.”

8. Execute the project. It will install the modules you selected.