Life without IE in the Configuration
In a previous blog post on the re-factoring changes that were done for FP2007 I listed out the components that were re-factored. One of these was Internet Explorer. Now generally I would say that most customers are happy not to have IE coming into most of their runtimes through a dependency check. However, there were also some things that customers got "for free" by having IE in the runtime. What I mean by that is that IE brought in a whole host of dependencies into the runtime that may have inadvertently satisfied other dependencies without you knowing it. Because IE is no longer coming into the runtime other behaviors are now apparent.
The most common behavior we get questions on is that, in FP2007 runtimes with Explorer Shell, the menu toolbar is not showing up any more- this is one that allows you to select "File > New", or "Tools >Folder Options" etc. This is actually the "correct" behavior in a basic runtime - if you build a "Winlogon Sample Macro" runtime with Explorer Shell in SP2 you will see the same thing! The reason for this now displaying in FP2007 runtimes is that one of the IE dependencies that you got for free is missing, and has to be added manually to the runtime. The component that populates the menu toolbar is Primitive:browselc - simply add this to your runtime, with minimal footprint impact.
- Lynda
Comments
Anonymous
February 06, 2007
A customer raised an issue a few weeks ago about RunOnceEx no longer working in a configuration thatAnonymous
February 14, 2007
As most of my last few posts have been about the re-factoring work done in FP2007 you may all be awareAnonymous
December 16, 2008
If you are using XPe Feature Pack 2007 (FP2007) you will know that we did a lot of re-factoring work