In this new series, we’re going to highlight some of the new features that we introduced in Application Virtualization Explorer (AVE), version 2.3, released in December last year (gosh, sounds like a long time ago when said like that!).

After looking at the basics of Virtual File System (VFS) and how the data behaves in the client for VFS virtualized directories in the previous articles in the series, let’s finish up the discussion of VFS folders by looking at one specific – rather interesting – bug (because that’s what it must be) when it comes to fully virtualized folders and the whole concept of isolation.

As I wrote previously, I had the opportunity to go to the HP’s biggest European [enterprise] event of the year, Discover 2011, last week, held in the city of Vienna in Austria. To be honest, I did not really know what to expect since I’m not all that familiar with HP’s solutions in virtualization area and it was initially a little bit out-of-place experience for an application –focused guy like me.

My earlier how-to article about doing App-V package branching operation using AVE was otherwise correct, but if you are intending to use your branched packages in App-V’s traditional Management Server infrastructure, there’s couple of additional details you must attend to in order to be able to import your branched packages in.

So, in the last week there was a first (European) App-V User Group day, that was held in Microsoft NL’s offices at Schiphol / Amsterdam. Like almost a 100 others, I was there to attend the event and even though I did not have my own presentation, I got my share of publicity as well.