Oh man, I cannot believe that the old issue kind of came back to haunt us. Back in the last year we fixed an issue in our App-V -related products that caused all App-V 4.6 packages to be flagged as 64-bit packages, now it was the reverse.

Windows Team blog has just announced, for the first time publicly, development and the details of App-V 5.0. Along with the new App-V version. Along with the next App-V version, the blog post also announced Microsoft’s User Environment Virtualization (UE-V) product (which was previously known with codename “Park City”).

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!).

When we announced possibility to test upcoming (and now released) AVE 2.3 version back in the few months ago, I promised that we will give out two complimentary licenses for two of the feedback submitters, drawn randomly.

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.

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.

We opened up a beta testing opportunity for upcoming Application Virtualization Explorer, version 2.3 a few weeks ago. At that post we also announced new features that were going to be in the product and that were already available in the beta as well.
While the new features mentioned will be getting a more detailed coverage in the upcoming weeks, I just wanted to write to tell about few new features which the beta does not support but will be in the actual 2.3 release.

We have been working on the next “major minor” update to the Application Virtualization Explorer Professional -product for a while now, and since the release time is now starting to get close, I would like to announce opportunity for you to participate in beta testing. If you are interested in trying out AVE 2.3, and to […]