So it’s no secret that one of the major improvements to come along with the App-V 5.0 SP2 Beta is the way we now handle and support shell extensions and runtime dependencies. Let’s take a closer look…
They are finally here! Probably the most requested feature when we talked about improvements for the App-V Sequencer.
This is what we would see pre-SP2 for App-V 5.0:
An extensive list of shell extensions are now fully supported, including:
- · Context menu handler
- · Drag-and-drop handler
- · Drop target handler
- · Data object handler
- · Property sheet handler
- · Infotip handler
- · Column handler
This means shell extensions such as the ones you get with WinRar are now supported when delivering via App-V. The great thing about all of this is no extra work is required.
Shell extensions show themselves inside the AppxManifest.xml:
Another thing we support is ActiveX controls and Brower Helper Objects:
ActiveX controls are now registered and supported via the AppxManifest.xml
The example above shows the control registered by Flash Player, this is used for things such as Internet Explorer integration. This means RunVirtual is no longer needed for this scenario, unfortunately the application still has to be published globally for this to work however.
Browser Helper Objects
Another extension we support are browser plugins, again aiding scenarios where we need applications to integrate with IE.
The example above shows the plugin Adobe Reader registers for Internet Explorer. Once we publish it globally to the machine, no extra work is required, the next time we open up Internet Explorer we will see the plugin is available to be enabled:
Again this means the RunVirtual feature doesn’t need to be utilised in this instance.
The other leap forward brought with SP2 is the how we now automatically package and deploy SxS Assemblies, most commonly in the form of VC++ run-time dependencies and MSXML.
These are automatically detected, the great thing about this is that is regardless of whether they are already on the sequencing machine or not, this is done by scanning the executable for any dependencies. On the client side, we will check for the presence of the required SxS and if it is not there it will be automatically installed.
You can review captured dependencies after sequencing also within the report.xml file:
Of course if you don’t want the Sequencer to automatically capture these dependencies there you can stop the behaviour by going to Tools -> Options in the Sequencer: