We have had the 32-bit fixup tool available for a while (to correct issues in App-V 4.6 packages saved out from AVE prior to version 2.2.6), but since the recent events there appeared to be a need to do the opposite as well.

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 the interest of full disclosure, I was recently contacted by a publisher who asked if I would like to review a new book, called Microsoft Application Virtualization Advanced Guide and written by an Argentinian(?) guy called Augusto Alvarez. As the topic sounds interesting enough, I was actually glad to have an opportunity to take a closer look at this book I actually already had heard about before.

Recently I was involved with the customer who uses, amongst the traditional App-V Management Server –based RTSP publishing, a HTTP publishing script that was posted in the App-V Team’s blog mid-2010. This script constructs necessary APPLIST information out of manifest XML files detected on a virtual directory, but unfortunately it has some shortcomings which I decided to fix and present an enhanced version here as a replacement.

Back in the last November, Sebastian Gernert who works as a Microsoft’s Support Escalation Engineer wrote an article about fixing Volume Shadow Copy –related issue with the App-V Client in the German App-V blog (browse the site with Chrome and you get handy translation prompt if you don’t read German).

While traditionally I have been a fan of doing App-V (and before that, SoftGrid) sequencing by using a locally installed virtualization software (CHV, Client Hosted Virtualization) like VMware Workstation, for some time already I have actually resorted to using our Hyper-V environment for the sequencing purposes. This is largely because I’m using a laptop almost 100% of the time, and near ultra-portable laptop is not perhaps the best platform for doing client-side virtualization due to necessity of needing external hard drives and so forth.

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.

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!