Move Version Assembly code out of chrome_elf.

chrome/app/version_assembly/README

Index: chrome/app/version_assembly/README
diff --git a/chrome_elf/README b/chrome/app/version_assembly/README
similarity index 60%
rename from chrome_elf/README
rename to chrome/app/version_assembly/README
index b657437375641fe34d6e97393f8208006489bc8c..7258895f622116a0921c1e25d1424053663c93ff 100644
--- a/chrome_elf/README
+++ b/chrome/app/version_assembly/README
@@ -1,9 +1,10 @@
-Chrome Early Loading Framework (aka ChromeELF)
+Chrome Version Assembly
 
-chrome_elf.dll is shipped in Chrome's version directory to ease updates,
-and is loaded early in chrome.exe's lifetime. This is done by turning the
-version directory into a private assembly which refers to chrome_elf.dll
-(http://msdn.microsoft.com/library/aa374224.aspx).
+The chrome version assembly makes it possible for load-time dependencies of
+chrome.exe to be shipped in Chrome's version directory to ease updates.
+(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 which uses this
framework)/(e.g., chrome_elf.dll)

Shorter and makes this comment more future proof :)

[Cait (Slow), 2014/01/14 16:11:29]

Done.

+is done by turning the version directory into a private assembly which refers to
+any DLLs that chrome.exe needs to know about.
 

[gab, 2014/01/13 21:43:37]

Add the following here I'd say:

New DLLs should be added as <file> entries in
"version_assembly_manifest.template".

[Cait (Slow), 2014/01/14 16:11:29]

Done.

 In an ideal world, this would be done by embedding an application config in
 chrome.exe that would refer to the proper version directory via a