I've recently upgraded from EVC4 to VS2005 IDE and have found that some of my CE projects when built do not behave the same as when compiled with EVC4. They are driver projects so not very easy to debug. Are there any recommended compiler and linker settings for VS2005? :roll:
VS2005 beta had a bug that DllMain was never called in DLLs. I have not tested that in VS2005 release.
Are you sure that your drivers don't have some hidden bugs? And be sure not to use internal windows structures, some of them have changed in WM5.
Related
Hi,
I've been using emBedded visual C++ for 2-3 years writing application for pocket PC ( Mainly Ipaq'a).
I've recentrly invested in a Xda but when I attempt to "update my remote output file" from with embedded VC ++" i get the following error:
" Microsoft Active sync connection server failed, Please make sure active sync is running and retry the download etc.."
Of course Activate sync is running, and running correctly, Has anyone had this issue before ?
I can manually copy my executable to my device and run it,but then I can't debug. I'm in the process of download VC 4.0 and going to try that, but really wold like to runing in under the 3.0 version.
Any comments would be appreicated.
Bad news dude, eVC++ works only with PocketPC 2000 + 2002. The development environment you'll need to develop on 2003+ is either eVC++ 4.0 or Microsoft Visual Studio.NET.
Thanks for the update,
I've installed Embedded VC 4.0 and the SP3, Now I can download to my XDA which is great.
Now I want to maintain backwards compatiable and download to my ipaqs in 2002, I can't change the actiive configuration to PPC2002
Is there a way to compile my application for both 2002 and 2003 using VC 4.0 or do I need to maintain both IDE's
Sorry but there's no way to maintain both 2K2 and 2K3 targets from eVC 4. You can have the same set of source code but eVC 3 + 4 have different project file types. Have a project per IDE containing the same source code. Just remember when you add files to the project you're working on, remember to add the files to the other platform's project as well.
Happy coding!
-Timbo.
dear all
I have been practising with some sample codes in evb and would like to test them out on my xda. I need educating on how to compile (make) an evb application and package same for installation on my xda. thanks in advance. I looked in eVB tools and got nothing.
ajanaman
XDA's are PocketPC 2003 devices and can not be used for "live" debugging from within the eVB IDE debug environment. Also the 2003 devices need the eVB runtimes installed on them in order to run eVB programs. Checkout www.devbuzz.com for guidelines. HTH.
I have a Qtek S200 with:
Microsoft Windows Mobile 5.0 OS 5.1.195 (Build 14928.2.2.0).
and
intent Java MIDlet Manager Runtime MIDP 2.0: v10.1.7.545 (Build 20051117)
I want to develop a MIDlet which needs file access and/or camera access. I know that device needs the optional packages (JSR-75 PDA-API and JSR-135 Mobile Media API) to accomplish that. And it seems that these optional packages are not supported by the MIDlet Manager.
I have tested this MIDlet already on a smartphone (Nokia N73). The Java Micro Edition of this Phone supports several Optional Packages. It can not be possible that a PDA provides less functionalities than a Smartphone.
1. Is it possible to upgrate the JVM (MIDlet Manager) on the device? So that I can use these optional packages.
2. Does anybody know which MIDlet Manager supports these functionalities?
I have found a newer version of the intent Java MIDlet Manager
Runtime JTWI 1.0: v11.1.7.1023 (Build 20060907)
This version provides the optional package JSR-75 which is needed for file access.
I found a download here: http://wronek.wikidot.com/java-wm
But this version does not provide the Multi Media API JSR-135 which is needed to use the devices build in camera.
So if anyone knows an other MIDlet Manager please reply.
I've found an other MIDlet Environment which supports file access (JSR-75).
It is the IBM J9. The installation of this Environment is a bit tricky but the GUI of this MIDlet Environment is more beautiful than that of the intent Java midlet manager.
Here you can find a good installation discription:
http://www.markus.brosch.net/?p=111
What additional software does one have to load to enable JSR-82 (Java bluetooth) dependant midlets to run? I have already updated my TOA midlet manager to the latest version 1036, but it seems some WM5 functionality is still missing. Are there modified DLL's or additional JAR files required that will provide this?
Hi All,
I am using VS2008 to write C# codes for a Windows Mobile 6.5 device. I know that Trace.WriteLine could be used to trace a program for a non Windows Mobile project However, when I try to use Trace.WriteLine in a Windows Mobile 6 project, I receive the following compilation error :
CS0117: 'System.Diagnostics.Trace' does not contain a definition for 'WriteLine'
I find that if I use Debug.WriteLine, then the mobile project compiles OK. But due to some technical issues I have to stick to the "release" build in this mean time. Does anyone know of other ways to trace a C# program in a windows mobile project, i.e. write debug messages to the VS2008 output window.
Thanks for any suggestion.
Regards
Lawrence
How to trace C# code in Windows Mobile 6.5
Hi All,
In fact, I have a downloaded opensource VS2008 solution with a C++ DLL project and a C# Application Form project. The C# project calls the DLL created in the C++ project. Both the two projects have a "release" config but the C++ DLL project doesn't have a usable "debug" config. The original opensource solution could be compiled and run OK if both of the two projects are in "release" mode.
However, I want to turn the two projects into "debug" mode and add debug/trace statements (Debug.WriteLine, Trace.WriteLine) in the two projects. For the C# project it is trivial but for the C++ project I find no way to do this. If I turn the C# project in "debug" mode while keeping the C++ project in "release" mode, the solution rebuilds OK but when I deploy the projects into my Windows Mobile 6.5 device, an exception occurs complaining that the "debug" mode DLL (i.e. the DLL with an extra "D" in its name) could not be found.
Does anyone know of an easy way that I could create a "debug" config from the existing "release" config for the C++ project so that I could turn the whole solution into "debug" mode, or could I re-config the "debug" mode C# project so that it could use the "release" mode DLL created in the "release" mode C++ project ?
I am sorry if I have asked a too naive or too hard question as I am mainly using Java and am new to the VS2008 C++/C# environment.
Thanks for any suggestion and any pointer/link would be appreciated.
Regards
Lawrence