windows-ce

I've succefully built STLPort and Boost c++ for Windows CE 6.0. I can run application with Windows CE 6 and STLPort both in debug end release mode. I've built boost with the following batch file: @echo off cls :build :release echo building boost in release shared library bjam ^ --with-system ^ --with-chrono ^ --with-date_time ^ --with-thread ^ --with-atomic ^ toolset=msvc-9.0~CEPlatform ^ variant=release ^ threading=multi ^ stdlib=stlport-5.2.1 ^ link=shared ^ runtime-link=shared :debug echo building boost in debug shared library bjam ^ --with-system ^ --with-chrono ^ --with-date_time ^ --with

When exiting my .NET CF 3.5 application on the Motorola MC3100 (CE 6.0 version only) I get the error message "Application xxx has encountered a serious error and needs to shut down". I then need to warm boot the device for the application to work again. This code works fine until the application is shutdown and it only fails if a font is set on a control in the application. Everything also works fine on .NET CF 2.0 and all of the other Motorola, Intermec, Psion, HHC devices I have tried with .NET CF 3.5. Here is my current test code: [MTAThread] static void Main() { Control oCtrl = new Control

I have an application written in C# targeting .NET Compact Framework 3.5, running on Windows CE. From time to time, operations lasting for a second or so are being performed on the UI thread. I currently set the Cursor.Current property to indicate that the application is busy, but this does not prevent mouse events from eager users to queue up. This sometimes leads to unintended clicks. What is the best way to ignore queued mouse messages on the .NET Compact Framework platform? Sadly, the code has to run on the UI thread. Disabling the controls won't help you, as I've found from my POS

I'm developing a console application that is supposed to run under WinCE 6.0 and WinCE 7.0 . I'm using C# , Compact Framework 2.0 for different compatibility reasons. My application is started by an external runtime called TwinCAT (from Beckhoff). Within this application, my teammate used a function block called nt_startProcess (documentation here ) that is in charge of starting my application on demand. My problem - Two different behaviors depending on the OS : When started manually (without TwinCAT) from a cmd line : My application behaves properly on both systems. It means that, the

I've been through all of the Stack Overflow answers search comes up with, and neither Google or Bing are showing me any love. I need to know when a network cable has been connected or disconnected on a Windows CE device, preferrably, from a Compact Framework application. I realize I'm answering my own question here, but it was actually a question asked of via email, and I actually spent quite a while finding the answer, so I'm posting it here. So the general answer for how this is detected is that you have to call down into the NDIS driver via an IOCTL and tell it that you're interested in

I have a WinCE device. Is it possible to connect to the device from visual studio to view the following Folder structure. Applications running. Registry values. Is there any other ways to view these items? Where can I get more information on this? yms Folder structure. Remote File Viewer Applications running. Remote Process Viewer or Remote Spy Registry Values. Remote Registry Editor EDIT: If your device does not have ActiveSync, you should read this MSDN article on how to connect to Windows CE without ActiveSync Summary of the MSDN article: Prepare the device: Copy the following files to the

What tools do you know, other than those in Visual Studio, to analyze performance bottlenecks in a Windows CE/Mobile application? I'm looking for something like AQTime for CE/Mobile, to profile C/C++ applications compiled to native code. I haven't found any such tools for WindowsMobile for native development. The closest I've found is the EnTrek toolset (CodeSnitch / ProcMan), but they aren't really profiling tools. http://www.entrek.com/products.htm What we did do is build own own profiling support into our own products using the Vistual Studio "/callcap" switch for VC++. Using that switch