• Home
Name Date Size #Lines LOC

..--

DEPSD03-May-202420 32

OWNERSD03-May-202465 33

READMED03-May-2024902 1613

chrome_elf.defD03-May-2024214 96

chrome_elf.gypD03-May-20241.4 KiB6463

chrome_elf_main.ccD03-May-2024537 2110

chrome_elf_main.hD03-May-2024318 114

chrome_elf_types.hD03-May-2024380 146

chrome_exe_manifest.templateD03-May-2024360 1010

chrome_exe_manifest_action.gypiD03-May-20241.1 KiB3431

ntdll_cache.ccD03-May-20241.9 KiB5232

ntdll_cache.hD03-May-2024458 166

ntdll_cache_unittest.ccD03-May-2024915 3320

version_assembly_manifest.templateD03-May-2024253 88

version_assembly_manifest_action.gypiD03-May-20241.2 KiB3733

README

1Chrome Early Loading Framework (aka ChromeELF)
2
3chrome_elf.dll is shipped in Chrome's version directory to ease updates,
4and is loaded early in chrome.exe's lifetime. This is done by turning the
5version directory into a private assembly which refers to chrome_elf.dll
6(http://msdn.microsoft.com/library/aa374224.aspx).
7
8In an ideal world, this would be done by embedding an application config in
9chrome.exe that would refer to the proper version directory via a
10probing\privatePath attribute (http://msdn.microsoft.com/library/aa374182.aspx).
11This would allow us to refer to dlls in the version directory without having to
12make the version directory itself into an assembly. It would also avoid naming
13conflicts (as the WinSxS dir and GAC both take precedence over private
14assemblies when searching for dlls). Unfortunately, the probing\privatePath
15attribute is only supported for Windows 7 and later.
16