How to deploy application to WEC 2013 RRS feed

All replies

  • Did you go through the WEC2013 release notes? it has the list of issues and its workaround on Remote tool, Application Debugger and Deployment.


    Thursday, June 27, 2013 12:46 PM
  • Thanks Vinoth.

    I Just go through all the release note in WEC2013.
    But didn't realize that what issue might cause my problem.

    Could you point me out what is the possible reason cause this issue?

    Thank you.

    Thursday, June 27, 2013 2:10 PM
  • Refer the following MSDN document for debugging application in Windows Embedded Compact 2013.

    Section: Attach to the Application Debugger (Compact 2013)

    Following steps may help,

    You have to run 2 instances of VS 2012 to debug application from VS2012.

    • Launch 1st instance of VS2012 and open the OS Design solution or NK.BIN file. Download the image to your device. This instance is used for debugging your OS image.
    • Launch 2nd instance of VS2012 where you develop application for Compact 2013.
    • Now go back to 1st instance of VS 2012 to set it up to communicate with 2nd instance.
      • Run ipconfig –d  from target control command and note of the 1st instance device’s IP address.
      • Add  <drive>\%prog files%\common files\microsoft shared\embedded tools\corecon\11.0\target\wce800\<cpu> to your 1st instance’s alternate release directory or copy all of its content to the release directory of 1st instance of VS 2012.
      • Run ConManClient3.exe from PB target control
      • Run CMAccept3.exe from PB target control
    • Now go back to your 2nd instance of VS 2012 to communicate with the device connected to 1st instance.
      • From VS menu select: Debug->[Your Project] Properties
      • Select “Debug” view in properties windows, and enter in the IP address of 1st instance  (that you have noted earlier in above steps)
      • Save the setting
    • Now your setup is ready to debug.



    Friday, June 28, 2013 6:22 AM
  • Whilst this is not your solution, you will also get the message:

    ""No connection could be made because the target machine actively refused it"

    if you try to run a Managed Code app on a system without .NET CF.

    DJaus Snr SW Dev (Embedded Systems and .NET)

    Friday, June 28, 2013 8:15 AM
  • Also if you aren't running a development system, ie the OS is on the system and running, or its running without the required App development tools, then you will need to copy the CoreCon file to the target and manually run ConManClient3 and Cmaccept3 on the target. is now able to generate a cab file to install files on a target Compact 2013 system.

    You can create a project using it to generate a OS subproject to encompass the 6 files.

    When the subproject is built, not only does it add the files to the OS, there is also a cab file in the release directory, that will add them to an existing system (that has the OS Install components). 

    DJaus Snr SW Dev (Embedded Systems and .NET)

    Friday, June 28, 2013 8:20 AM