It so happened a while ago that I was on consulting day for a customer and we needed to make smallish update to an existing App-V package I originally did with Sequencer (because AVE does not currently have a monitoring functionality nor package creation from scratch). This update was only about adding a bunch of files to the sequence (some additional data/definition files for the application within) and as I did not had AVE installed on their packaging machine, I went with the usual Sequencer route. I soon discovered that I shouldn’t have done that…

In the previous article of AVE’s scripting capabilities, we discovered how AVE implements the basic App-V scripting capabilities – but in much smarter manner and easiness lacking in any other App-V –related tool there is. In this installment, we will see how to take scripting a bit further, by adding additional execution capabilities for our […]

In the earlier blog post, we have saw how App-V supports scripting for added package functionality and how it is configured by using the built-in tools (i.e. Sequencer) or manual methods; let’s now look at how our Application Virtualization Explorer (AVE) can make the process much easier for you regardless of the scenario.

Having been inspired by a recent blog posting by Tim Mangan about currently known issues in package branching (and my own previous experiences of the same), both in 4.6 and 4.6 SP1 versions of the App-V Sequencer, I thought about to write a quick and short howto for doing branching operating with our Application Virtualization Explorer (AVE).

I’m happy to share with you that we have partnered with one of the leading traditional setup authoring toolkit vendors, InstallAware, and they will be bundling our technology in the upcoming 2012 release of their product line. More information on the new App-V capabilities can be found from InstallAware’s news release at http://www.installaware.com/news-installaware-2012.htm. But did you know […]