The App-V community has long been a very giving group of professionals, going back to the old Softricity days. We post on the forums and share recipes on how to sequence apps. Some of us post on blogs and even produce instructional videos. And while I don’t tweet, I certainly see signs of a lot of sharing happing via twitter.
One of the things that Softricity, and then Microsoft, has always said about sequencing is that you cannot sequence the internet explorer itself. Plugins that reference and use the local client IE yes, but not IE itself.
I have always felt that this was incorrect. That the components all are in user space and that given sufficient effort, one could figure out what to put into the package and get a virtualized IE. Until recently, I never saw a compelling enough reason to want to put in such effort.
To learn more and to read the entire article at its source, please refer to the following page, IE6 on Windows 7 App-V Sequence: CSS should “Open Source” the Recipe- Tim Mangan: Confessions of a Guru - www.tmurgent.com
Article Tags