1Chrome Version Assembly 2 3The chrome version assembly makes it possible for load-time dependencies of 4chrome.exe to be shipped in Chrome's version directory to ease updates (eg. 5chrome_elf.dll). This is done by turning the version directory into a private 6assembly which refers to any DLLs that chrome.exe needs to know about. New DLLs 7should be added as <file> entries in "version_assembly_manifest.template". 8 9In an ideal world, this would be done by embedding an application config in 10chrome.exe that would refer to the proper version directory via a 11probing\privatePath attribute (http://msdn.microsoft.com/library/aa374182.aspx). 12This would allow us to refer to dlls in the version directory without having to 13make the version directory itself into an assembly. It would also avoid naming 14conflicts (as the WinSxS dir and GAC both take precedence over private 15assemblies when searching for dlls). Unfortunately, the probing\privatePath 16attribute is only supported for Windows 7 and later. 17