Developing WM5 app, runs differnet in Debug versus Release
-
I'm developing a small app for WM5 and it is using FindFirstFile() and FindNextFile(). These work just great in the WM5 emulator in debug mode. I created a CAB file and ran it on my Axim, but it didn't work correctly. I left the state to Release, as opposed to Debug and ran it in the WM5 emulator, and got similar problems. I think this is working differently for more then just these, but I'm not sure. The code I am having problems with is looking for a specific file by pattern, and then looking to see if there are others that follow the same pattern; I'm looking for the newest dated version of the file that fills the pattern. like \Windows\abc*.txt it works great in debug mode on the emulator, but not so on my Axim or in release mode on the emulator. Does anyone know what is happening here?
-
I'm developing a small app for WM5 and it is using FindFirstFile() and FindNextFile(). These work just great in the WM5 emulator in debug mode. I created a CAB file and ran it on my Axim, but it didn't work correctly. I left the state to Release, as opposed to Debug and ran it in the WM5 emulator, and got similar problems. I think this is working differently for more then just these, but I'm not sure. The code I am having problems with is looking for a specific file by pattern, and then looking to see if there are others that follow the same pattern; I'm looking for the newest dated version of the file that fills the pattern. like \Windows\abc*.txt it works great in debug mode on the emulator, but not so on my Axim or in release mode on the emulator. Does anyone know what is happening here?
OK. I figured this out. It was a missing include file. Kind of strange that Visual Studio in Debug mode would reconcile these without any warnings, and then just skip over these function calls when run in Release mode or on the device. I don't know if there is some build setting to at least warn me about this; if anyone knows of a warning, let me know. Thanks