chrome_elf/README - Issue 53793002: Initial implementation of Chrome Early Loading Framework

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: chrome_elf/README

Issue 53793002: Initial implementation of Chrome Early Loading Framework (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Created 7 years, 1 month ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
(Empty)
	1 Chrome Early Loading Framework (aka ChromeELF)

	2

	3 chrome_elf.dll is shipped in Chrome's version directory to ease updates,

	4 and is loaded early in chrome.exe's lifetime. This is done by turning the

	5 version directory into a private assembly which refers to chrome_elf.dll

	6 (http://msdn.microsoft.com/library/aa374224.aspx).

	7

	8 In an ideal world, this would be done by embedding an application config in

	9 chrome.exe that would refer to the proper version directory via a

	10 probing\privatePath attribute (http://msdn.microsoft.com/library/aa374182.aspx).

	11 This would allow us to refer to dlls in the version directory without having to

	12 make the version directory itself into an assembly. It would also avoid naming

	13 conflicts (as the WinSxS cache may override the lookup path from a private
	gab 2013/11/12 18:24:10 I think it's the GAC and the WInSxS folder (two di I think it's the GAC and the WInSxS folder (two different things AFAIU) -- they don't really have the power to "override", they're simply first in the lookup sequence, so they have the power intercept lookups for private assemblies. I'm fine with either wording that mentions this more or less...
	14 assembly). Unfortunately, the probing\privatePath attribute is only supported

	15 for Windows 7 and later.

OLD	NEW