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.

One common mistake people tend to do when trying out the whole application package “side-by-side” functionality of App-V – i.e. running separate packages of the same application suite on a same machine – is to not be careful enough about how to name each individual application.

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.

After adding some new features to and fixing newly discovered issues in a beta of upcoming Application Virtualization Explorer, version 2.3, we are releasing a second beta build today. And that’s not all, we also have a release date set now as well!

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.