Shell Extensions and Runtimes with App-V 5.0 SP2

Share on facebook
Share on twitter
Share on linkedin
Share on reddit
Share on stumbleupon

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…

Shell Extensions

They are finally here! Probably the most requested feature when we talked about improvements for the App-V Sequencer.

Before

This is what we would see pre-SP2 for App-V 5.0:

Now

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

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.

Runtime Dependencies

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:

 

Leave a Reply.

20 thoughts on “Shell Extensions and Runtimes with App-V 5.0 SP2”

  1. If we want to Virtualise an ActiveX component today in AppV 5.0 SP1 is the only way RunVirtual?  If our requirement is that we have 2 different versions of an ActiveX to isolate from each other then that doesn't get resolved by RunVirtual because it all runs in one big bubble.  For example, can you still create the I.E shortcut and virtualise each ActiveX separately as you could in AppV 4.x using AppV 5.0 SP1 – is this what you are specifically resolving with SP2 and if so how long till the release?

  2. Tried sequencing Salesforce for Outlook plug-in as an add-on in App-V 5.0 SP2. But while launching the shortcut, natively installed outlook is not recognizing virtualized salesforce plug-in. Does shell extensions, will work only for browser plugin or for all other plug-ins also.. I am stuck up here, can u pls help me out…. Am i missing anything???

    • Hi there, I haven’t seen this functionality working with anything other than Browser helper objects and ActiveX Controls. You may need to use RunVirtual for your scenario.

  3. We have virtualized many ActiveX controls pre SP2 without much issue. To access the IE with the virtual plug-in we removed all native shortcuts to IE and published one with the /appvve switch. Everything is published on a per user basis

  4. Hi Thamim,

    I am working on appv5.0 SP2 packaging.
    one of my shortcut of application gives error that “409: ACTIVEX Component can’t create objects”

    any suggestions on this?

  5. Hi Thamim,

    Is shell extension supported only in global publishing scenario? It doesn’t seem to be the case with WinRAR and Notepad++. I have sequenced WinRAR with APP-V 5.0 SP3 and published to User group and I see the context menus appeared automatically without any extra work. However, for ActiveX and I had to create run virtual key for IE process. Could you please tell me if I’m missing anything with Shell extension?

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.