I have a legacy application that is dependent on certain system32 DLLs (hardcoded API calls). My ultimate goal is to make this application OS independent (at least between XP SP2 and Vista SP1). So... I have a dependency chain as follows:
App.exe -> NETAPI32.DLL -> MSVCRT.DLL -> NTDLL.DLL -> ADVAPI32.DLL, etc. etc. (All XP-based DLLs)
With the goal being OS independency, it seems that I should include at least some of these DLLs in the virtual bubble. I know this can be dangerous, considering the differing API calls, etc.
So I guess my question is: has anyone else run into this problem? My experience so far is that when I start including these system DLLs in the package, the errors come pooring out. Is there another solution?
Thanks,
Clint