ASMS folders in Win7
Posted: Wed Jun 08, 2011 8:51 am
I'm trying to do a reverse-engineer of Yumeyao's Visual C++ runtimes true addon for Win7, because the switchlesses always fail unattended and need to be fudged with more cumbersome means post-install. Win7 does away with the ASMS folders on the install source that XP has (which VC++ 2K5, and 2K8 are deployed from in Yumeyao's addon) in favor of distributing the files in a zillion winsxs folders.
Is there any transition layer within Win7 that replaces the ASMS distribution structure and automatically distributes the runtime files to their proper winsxs directories? Parsing the MSI in Orca and painstakingly slotting each and every file into a winsxs folder is such an error-prone way to do it that it's not practical, but I was wondering if Windows had some sort of internal 'shiv' for that which sorted the files much like the system32/syswow64 and Program Files/Program Files (x86) divides are made fully transparent to installers. Even better if Setup has some sort of backward compatibility that lets you integrate the ASMS folder structure in the install source and have Setup automatically recognize and migrate it.
I've found no documentation online saying one way or the other how Win7 treats that old ASMS functionality or what the preferred replacement means is for installers. Anyone familiar enough with the internals of that to offer any insight? Could potentially affect a lot of different addons.
Is there any transition layer within Win7 that replaces the ASMS distribution structure and automatically distributes the runtime files to their proper winsxs directories? Parsing the MSI in Orca and painstakingly slotting each and every file into a winsxs folder is such an error-prone way to do it that it's not practical, but I was wondering if Windows had some sort of internal 'shiv' for that which sorted the files much like the system32/syswow64 and Program Files/Program Files (x86) divides are made fully transparent to installers. Even better if Setup has some sort of backward compatibility that lets you integrate the ASMS folder structure in the install source and have Setup automatically recognize and migrate it.
I've found no documentation online saying one way or the other how Win7 treats that old ASMS functionality or what the preferred replacement means is for installers. Anyone familiar enough with the internals of that to offer any insight? Could potentially affect a lot of different addons.