Internet Explore consists of files like: iexplore.exe, ieframe.dll, mshtml.dll, shdocvw.dll, browseui.dll, wininet.dll, urlmon.dll, hmmapi.dll, ieproxy.dll, IEShims.dll, jsprofiler.dll et cetera. And as such the application isn’t fully removed until all parts are removed. they are dynamically linked and/or loaded at runtime) which all are a part of the application.
A componentized application consists of several files (e.g. It also contains resources, whether internally or externally. Point is: An application (usually) does not only consist of code. Heck, even Warlords (1) comes with several files: WARLORDS.EXE, WLC.LBM, SCENERY.LBM, RING.SJH, DRUMROLL.SJH et cetera. For Google Chrome we have files like chrome.exe, devtools.css, gears.dll, icudt42.dll, rlz.dll, back.png, checker.png, wow_helper.exe et cetera. To name a few: firefox.exe, application.ini, freebl3.dll, mozcrt19.dll, plc4.dll, xpinstall.js, browser.xpt, nsBadCertHandler.js et cetera. It is (like most applications) made from many parts. iexplore.exe doesn’t even contain the GUI for IE (I’ll go into details with that later on).ĭo you really think that deleting firefox.exe will remove all of Firefox? What about external resources, registry keys and what not? Firefox is not just a single part.
It is also the name for the entire package (e.g. Besides that Internet Explorer is not merely a GUI-shell around a rendering engine. It is a componentized (or modular/dynamically linked*) application and as such cannot be claimed to be one single file. statically linked with its resources), but it is not. It would’ve been true if IE was a monolithic application (e.g. I want this thread to be kept in a sober, technical tone and not become a flamewar. The reason behind this is that the tone in this thread is going in the wrong direction.
0 kommentar(er)
