MMC without IE (the solution)

  • Thread starter Thread starter JHZ
  • Start date Start date
J

JHZ

Hey Guys,

I saw a lot of posts regarding how to install MMC without IE, but no
answers. Well I've got one. Turn Off Auto-Resolve Dependencies.
Add MMC to the build in TD (Do not add HTML Help Engine or HTML
Rendering Engine, they are not neccesary and bring IE into the build)
Add (through a custom component or otherwise) the following registry
data
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer]
"Version"="6.0.2900.2180"

This registry key will allow MMC to start up successfully without
complaining that IE is not present.

Enjoy your new IE free build,
JHZ

PS Microsoft really needs to get their act together on this dependency
issue, this is ridiculous. The XPE team at Microsoft needs to go
through every component and every dependency and say
1. Does this really need this dependency
2. Can I modify this component so it doesn't need this dependency.
 
JHZ said:
I saw a lot of posts regarding how to install MMC without IE, but no
answers. Well I've got one. Turn Off Auto-Resolve Dependencies.
Add MMC to the build in TD (Do not add HTML Help Engine or HTML
Rendering Engine, they are not neccesary and bring IE into the build)
Add (through a custom component or otherwise) the following registry
data
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer]
"Version"="6.0.2900.2180"

This registry key will allow MMC to start up successfully without
complaining that IE is not present.
Click to expand...

Thanks. I just tried it and it works fine. Now I can include Device Manager
in my current build.

-Mike
 
JHZ, you rock. Thank you. For FP1 we're looking at some serious IE
refactoring to break up the long chain of dependencies from above IE, within
IE and below IE.

A feature having a dependency on another feature's reg key is one of the
biggest challenges we have in detecting dependencies (up there with WMI and
COM deps), for future versions of the product our team will need to invest
more heavily in the tools to grep through the source idenentifying things
like this.

Will also require adding the ability to cook components against registry
keys (i think i talked about that in the blog, linked below, last year).

Thanks again.

Andy
 
Hello,

I try your manipulation but I have a problem.
In fact, I create a new component whitout file but with your registry
data [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer]
"Version"="6.0.2900.2180".
After, in my run time I just add MCC without HTML Help Engine, HTML
Rendering Engine and Internet explorer and I add my new component but
when I do a "build depencies" there are 3 errors who aked tha i can add
HTML Help Engine for MCC and Internet explorer.

Can I help me please ?
 
Superman said:
I try your manipulation but I have a problem.
In fact, I create a new component whitout file but with your registry
data [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer]
"Version"="6.0.2900.2180".
After, in my run time I just add MCC without HTML Help Engine, HTML
Rendering Engine and Internet explorer and I add my new component but
when I do a "build depencies" there are 3 errors who aked tha i can
add HTML Help Engine for MCC and Internet explorer.
Click to expand...

Hi Superman,

You must ignore those dependency errors and build anyway.

-Mike
 
ah ok thank you but i have a question :
If i don't create a component with the registry data, are they errors
during the build ?
 
Back
Top