WinCE Remote Debugging: “No process is on the other end of the pipe.”

I have a new WinCE platform to port our project onto, and was getting “No process is on the other end of the pipe” when I would try remote debug the app, after successfully deploying via WinCE development without Active Sync on Win 7 as previously mentioned.

The application would also silently refuse to run when launched from WinCE explorer or the command shell.

I created a new default application, and it remote deployed and ran. So I knew there was something special with my application.

I tweaked lots of things that had zero impact, but in the end adding Wininet.lib and calling InternetOpen caused my test app to also not run. If I included the library as a depenacy but didn’t call InternetOpen the application runs fine, if I call InternetOpen it fails.

I suspect Wininet.dll is not present of the development WinCE 6 OS I have, and therefore the failure to load the .dll is pulling the executable down.

Email sent off to OS team, so I’m back onto a different project…

[Update: A few hours later…] Yip, wininet.dll has been removed.

WinCE SDK problems in Windows 7

For the last few weeks, my work project has not been building it’s WinCE target on my new Windows 7 PC. Each project would just say “skipping build”,

12>------ Skipped Build: Project: PROJECT_NAME_12 ------
12>
13>------ Skipped Build: Project: PROJECT_NAME_13 ------
13>
========== Build: 0 succeeded or up-to-date, 0 failed, 13 skipped ==========

and if I tried to edit the project properties (or build/clean/rebuild project only), I would get

The operation could not be completed

It then dawned on my to try a new project test, and the SDK was missing from the options:

A bit of focused searching found Windows CE: SDK Doesn’t Show up in Visual Studio 2008 post, and the solution worked for me with my Visual Studio 2005 SDK under Windows 7 also:

  1. Make sure Visual Studio 2005is not running. I also shut down the device emulator manager but you may not be using that
  2. Open a “Visual Studio 2005 Command Prompt” as Administrator. On Windows 7 just right click the short cut and pick the “Run as administrator” option
  3. Enter the following command: msiexec /package <the path to your .msi file>
  4. Install

You need to used the same steps above to uninstall the SDK as well (as compared to the Control Panel’s ‘Programs and Features’ options), otherwise it won’t uninstall correctly.