Windows Mobile version incompatibility?
|
Prev: The project could not be opened because it refers to a device platform that does not exist in your datastore.
Next: GPSID: GPS data in unattended power mode on WM6 device
From: Allan Phillips on 6 Oct 2008 11:38 No. I actually used the "Windows Mobile 5.0 SDK". I've now removed the 5.0 SDK and tried to install "Pocket PC 2003 SDK". However, it does not seem to install along with VS2005. It seems to insist on VS2003 (.NET). Is there a way to get "Pocket PC 2003 SDK" to install into VS2005? Thanks, Allan. <r_z_aret(a)pen_fact.com> wrote in message news:1b9ke49jjej7grnoi69ntiika919q8usp4(a)4ax.com... > On Sun, 5 Oct 2008 17:22:46 -0400, "Allan Phillips" > <allanephillips(a)gmail.com> wrote: > >>Thanks Christopher. >> >>I see that my .EXE shows a "Subsystem Ver" of "5.1" - so I guess that's a >>problem. >> >>Now I just have to figure out which compiler/linker setting will change >>that. > > Using the correct SDK should be sufficient. Did you really use the > Pocket PC 2003 SDK and really chose Pocket PC 2003 (ARMV4) as your > target?. > > >> >>Allan. >> >>"Christopher Fairbairn [MVP]" <christopher(a)christec.co.nz> wrote in >>message >>news:%23VyuP7yJJHA.2444(a)TK2MSFTNGP06.phx.gbl... >>> Hi Allan, >>> >>> "Allan Phillips" <allanephillips(a)gmail.com> wrote in message >>> news:eh5XrDyJJHA.5972(a)TK2MSFTNGP06.phx.gbl... >>>> I've just had one thought - this app was written using MFC. >>>> Is it necessary to include extra DLLs when building a Windows Mobile >>>> app >>>> that makes use of MFC? >>> >>> A couple of thoughts cross my mind. >>> >>> First take a second look at the output of the depends utility. Check the >>> "Subsystem Ver" field for your executable. In order to run on Windows >>> Mobile 2003 Pocket PC edition this field should probably have the value >>> 4.21. If the value is 5.0 or higher it indicates your application was >>> built against the Windows Mobile 5.0 or 6 SDKs and this will explain why >>> it will not run on WM 2003 devices. >>> >>> You may need to deploy MFC related DLLs depending upon how your >>> application is built. See for example the details provided in the >>> "Walkthrough: Packaging a Smart Device Solution for Deployment" article >>> available on >>> MSDN at http://msdn.microsoft.com/en-us/library/zcebx8f8.aspx >>> >>> Hope this helps, >>> Christopher Fairbairn >>> >> > > ----------------------------------------- > To reply to me, remove the underscores (_) from my email address (and > please indicate which newsgroup and message). > > Robert E. Zaret, eMVP > PenFact, Inc. > 20 Park Plaza, Suite 400 > Boston, MA 02116 > www.penfact.com
From: Christopher Fairbairn [MVP] on 6 Oct 2008 18:52
Hi, "Allan Phillips" <allanephillips(a)gmail.com> wrote in message news:eMGeUm8JJHA.2444(a)TK2MSFTNGP06.phx.gbl... > Is there a way to get "Pocket PC 2003 SDK" to install into VS2005? The Pocket PC 2003 SDK should be installed out of the box when the Smart Device Support option is selected. When you use the new project wizard to create a new Smart Device project you should see that Pocket PC 2003 is selected as the default target platform and one of the steps allows you to select other target platforms. This is the easiest way to ensure your application is compiling against the correct version of the header files and libraries etc. Alternativly you can have a go at providing the linker a commandline argument such as /subsystem:"WINDOWSCE,4.20" Hope this helps, Christopher Fairbairn |