Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(921)

Side by Side Diff: chrome/app/version_assembly/README

Issue 137373002: Move Version Assembly code out of chrome_elf. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 6 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 Chrome Early Loading Framework (aka ChromeELF) 1 Chrome Version Assembly
2 2
3 chrome_elf.dll is shipped in Chrome's version directory to ease updates, 3 The chrome version assembly makes it possible for load-time dependencies of
4 and is loaded early in chrome.exe's lifetime. This is done by turning the 4 chrome.exe to be shipped in Chrome's version directory to ease updates.
5 version directory into a private assembly which refers to chrome_elf.dll 5 (Currently, chrome_elf.dll is the only library which uses this framework). This
gab 2014/01/13 21:43:37 s/(Currently, chrome_elf.dll is the only library w
Cait (Slow) 2014/01/14 16:11:29 Done.
6 (http://msdn.microsoft.com/library/aa374224.aspx). 6 is done by turning the version directory into a private assembly which refers to
7 any DLLs that chrome.exe needs to know about.
7 8
gab 2014/01/13 21:43:37 Add the following here I'd say: New DLLs should b
Cait (Slow) 2014/01/14 16:11:29 Done.
8 In an ideal world, this would be done by embedding an application config in 9 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 chrome.exe that would refer to the proper version directory via a
10 probing\privatePath attribute (http://msdn.microsoft.com/library/aa374182.aspx). 11 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 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 make the version directory itself into an assembly. It would also avoid naming
13 conflicts (as the WinSxS dir and GAC both take precedence over private 14 conflicts (as the WinSxS dir and GAC both take precedence over private
14 assemblies when searching for dlls). Unfortunately, the probing\privatePath 15 assemblies when searching for dlls). Unfortunately, the probing\privatePath
15 attribute is only supported for Windows 7 and later. 16 attribute is only supported for Windows 7 and later.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698