views:

317

answers:

0

I am using a tool from Xenocode that can build a virtual application environment. Our application is complex, with several tools and executables that work together. Initially I used a xenocode tool to take a before and after snapshot to generate the original app. Since then I have modified the build script manually. Now I have to add a new sxs library (MFC and CRT) because one of the elements in the mix has been upgraded. I want to add the appropriate elements into the winsxs folder in the virtual application environment which looks identical to the real sxs folder structure. I did this in an XP based environment before by adding the .dll folder: e.g.

x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.4053_none_cbf21254470d8752

and the corresponding files in the Manifest and Policy folders.

However, in Vista and W7 the structure has changed a bit. In addition to the folder with the DLLs there is a Manifest folder (as in XP) with the manifests and the security catalogs and another folder called Catalogs with files with long GUIDs as filenames. Its difficult to tell at a glance how to find the right files in this folder that go with the new sxs files.

Does anybody know how to find all the files that are linked to a particular release of these DLLS?

Alternately is it possible that the Catalogs files are only used during the installation process and won't be needed in the virtual environment? I am going to try this anyway but this thing can find a lot of ways to fail so my experiment won't be conclusive.

Best Regards

MC