How to build on XP for Vista?

[DavidWhite]

I would appreciate some help getting my App to run under Vista. One of my internal customers now has Vista installed on his machine, and got the Microsoft dialog "an error has occurred ..." with my App.

Running Dependency Walker against my executable on his machine shows that DWMAPI.dll is missing (this is a Vista file, so this is confusing).

What do I need to do to rebukld my App to run on Vista? I am still in an XP environment. I am building about 200 files into 8 libraries into a single executable, using Multithreaded and Static.

Thanks for your help

David

[Jugoslav_Dujic]

Quoting - David White

I would appreciate some help getting my App to run under Vista. One of my internal customers now has Vista installed on his machine, and got the Microsoft dialog "an error has occurred ..." with my App.

Running Dependency Walker against my executable on his machine shows that DWMAPI.dll is missing (this is a Vista file, so this is confusing).

What do I need to do to rebukld my App to run on Vista? I am still in an XP environment. I am building about 200 files into 8 libraries into a single executable, using Multithreaded and Static.

Thanks for your help

David

No, you shouldn't rebuild your app for Vista. I don't even think that DWMAPI.dll is relevant in the whole story -- it's probably a delay-loaded dll or something that caused the Dependency Walker to be confused. If it were really missing, you would get a different error message.

I presume the error comes from different ways the OSes initialize... something. But the best way to find out is to debug it on Vista. Does it fail on all Vistas or just that one?

[DavidWhite]

Quoting - Jugoslav Dujic

No, you shouldn't rebuild your app for Vista. I don't even think that DWMAPI.dll is relevant in the whole story -- it's probably a delay-loaded dll or something that caused the Dependency Walker to be confused. If it were really missing, you would get a different error message.

I presume the error comes from different ways the OSes initialize... something. But the best way to find out is to debug it on Vista. Does it fail on all Vistas or just that one?

Jugoslav,

Thanks for this info. At present, I have no access to Vista. In fact, I understood that company-wide we were not migrating to Vista until the end of 2009, so this user in Spain reporting problems under Vista took me completely off guard.
depends also shows module errors against SHLWAPI.dll and MPR.dll but I don't think they are significant. What is intriguing is that all of the modules are shown as c:winnt... Is this an expected location under Vista?
Thanks,

David

[Steven_L_Intel1]

If the user upgraded an XP system to Vista, then C:WINNT could be correct.

[jarvusluntatintel]

David

I had this problem also that the office I work for does not allowany Vista machines (government security related)and we wanted to test products to make sure they worked with Vista. Using VMware, we were able to have virtual Vista machines that worked for testing and bug fixes. This is not a free fix, but it worked well enough for us.

[Steven_L_Intel1]

Microsoft Virtual PC is free.