Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
John Sheehan: Architecture and Engineering of Microsoft Application Virtualization (AppVirt)
Feb 10, 2009 at 9:51 AM-John
John Sheehan: Architecture and Engineering of Microsoft Application Virtualization (AppVirt)
Feb 10, 2009 at 9:49 AMYou are right. We deal not just with program state, but with all of the state that the application attempts to place on the system.
It would be nice to further explain how a single "capture" installation can target many "clients." More specifically, how would it deploy to different hardware, or versions of windows? Would you have to create a new image for each machine profile?
I think most of this is covered in the first video. Basically, a single image typically can be used for all machines. Of course, if the installer did something very different based on the hardware, it would be an issue. But, since we don't virtualize device drivers, this isn't something we see in practice. As far as different OS versions go, customers typically capture the install on the lowest OS version they want to support and then stream the image to all OS versions. From the application's perspective, it looks no different than if the app had been installed on the lower OS version and then it was upgraded to the new OS version.
Also, about the virtual file system, does it only redirect the original installed files? Or does it also redirect newer files created by the user (settings, for example)?
It has to do both. There is logic in the VFS to handle redirecting installation state and user state (i.e. settings).
John Sheehan: Inside Application Virtualization
Jul 07, 2008 at 9:29 PMJohn