> The user interface is the same as for VB and VID. You can pick the files you need to install, assign them to various folders, and build shortcuts just like InstallShield or Wise.

Hi Bob. Does a VFP developer need to know which files to include in the install (VFP runtime files too) and also know where each of these files go? For instance would the developer need to know VFP6RENU.DLL needs to go into the Windows system directory?

> It has the capability of building shared modules (.msm files) that can hold your common files like the VFP runtime stuff.

Perhaps this is the answer to the above question. We only need to figure this out once then?

From what I understand, Windows with then repair the install if one of the DLLs goes missing. Does each workstation keep these dlls or are these stored in a network location.

> Overall, I'm impressed. It looks like Microsoft really wants to get out of dll hell. Anyone else tried it yet?

Only installed it.

What I would like to see is if I put an EXE on our fileserver and a user clicks on it, Windows could figure out that it is a VFP6 (or VB or VC) exe and then install the runtime and all necessary DLL files needed for the app. And then if any new dlls come along (including VFP6 runtime DLLs), I can tell the app and the next time the user ran the exe it would do the upgrade.