none
Unable to debug C# apps on my Compact7 Device via either VS2008 or VS2008 Platform Builder RRS feed

  • Question

  • Hope someone can help me,

    I am trying to port our WinCE 4.2 C# app (plus its dlls) into a new ARM 7 board which is already loaded with a BSP and and a Compact 7 O/S image that includes .NET 3.5 support. (Besides the c# dlls the project also contains native code dlls which I am able to debug via a c++ test program under PlatformBuilder. So I am ok there). My problem is, not being able to debug even the simplest of C# programs, just a Main() function with a simple Console.writeline("Hello World");. I am simply no hiting the breakpoint inside main. I initialy tried debuging C# apps via PlatformBuilder (The C# project was initialy ported/compiled via VS2008 and then I added them to my PB SubProjects) but breakpoints in Main() never become active. Then I tried debugging via a second instance of VS2008 while the 1st instance was loading and debuging the O/S image via PB. In both cases I am able to connect and deploy the app + its dlls but it  never hits the breakpoint in main() which in this case it shows as active breakpoint. I know the application is running because I can see the Console.writeline() execute in the remote display. but still the breakpoint is not hit.

    1) should I even be trying to debug C# code via PlatformBuilder subprojects? is this valid?

    2) What am I doing wrong that my breakpoints are not being hit on my c# Main function on either method above?

    Thanks for any help, Jose

    Tuesday, March 12, 2013 8:10 PM

All replies

  • 1. Generally no (unless perhaps you need to debug JITed native code).

    2. May be a number of reasons.

    For example symbol loading issues, attach to managed projects is not enabled and so on.

    I would say try stepping into the projects with debugger from VS, do not use PB debugger at that time.


    This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, March 12, 2013 9:09 PM
  • Hi Ilya,

    Thanks for your reply.  I am sorry but can you explain what you mean by enabling Attach to Managed Projects? where do you  do this? (Under Debug there is an Attach to Process).

    I decided to remove all C# projects references from my PB subprojects and only leave the C++ ones . I connect to the target via (auto)Ether. I should mention that when I open my solution in PB it initially gives a popup stating "The project consists entirely of configurations that require support platforms which are not installed in your machine The project can not be loaded" but it does not mention which project. Still my OS Design and C++ Subprojects do load and deploy. Then I connect via the 2nd VS2008 containing my C# projects and start a debug from there. The VS output window only states that my project is deployed but the output window in PB shows the loading of modules and the Process viewer in PB shows my module is started. Still breakpoints are not hit in VS. While looking at the Remote Display it shows an hour glass but if I start it manually from the Remote Display it runs. Below is the output when my "'CTIEntryPointDummy.exe' " is started:

    8153391 PID:400002 TID:f502fa OSAXST1: >>> Loading Module 'mscoree.dll' (0xBD8843D0) at address 0x42950000-0x42962000 in Process 'NK.EXE' (0x85827AD0)
    PB Debugger Loaded 'MSCOREE.DLL', no matching symbolic information found.
    8154008 PID:366013e TID:f502fa OSAXST1: >>> Loading Module 'mscoree.dll' (0xBD8843D0) at address 0x42950000-0x42962000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8154008 PID:366013e TID:f502fa OSAXST1: >>> Loading Module 'ole32.dll' (0xBD857B1C) at address 0x41A20000-0x41B25000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8154008 PID:366013e TID:f502fa OSAXST1: >>> Loading Module 'rpcrt4legacy.dll' (0xBD857C54) at address 0x41BD0000-0x41C76000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8154008 PID:366013e TID:f502fa OSAXST1: >>> Loading Module 'lpcrt.dll' (0xBD858270) at address 0x414A0000-0x414A7000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8154008 PID:366013e TID:f502fa OSAXST1: >>> Loading Module 'bcrypt.dll' (0xBD8458AC) at address 0x43CD0000-0x43D22000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8154381 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'coredll.dll' (0xBD80DD6C) at address 0x40010000-0x40163000 in Process 'cgacutil.exe' (0xBD88C088)
    8154381 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'cgacutil.exe' (0xBD88C088) at address 0x00010000-0x00018000 in Process 'cgacutil.exe' (0xBD88C088)
    PB Debugger Loaded 'CGACUTIL.EXE', no matching symbolic information found.
    8155269 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'locale.dll' (0xBD80F260) at address 0x40170000-0x401B1000 in Process 'cgacutil.exe' (0xBD88C088)
    8155733 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'normalize.dll' (0xBD80F704) at address 0x401E0000-0x40200000 in Process 'cgacutil.exe' (0xBD88C088)
    8155733 PID:4c6005a TID:5a80052 CePerf.dll is absent - performance data will not be recorded
    8155733 PID:400002 TID:5a80052 OSAXST1: >>> Loading Module 'mscoree3_5.dll' (0xBD88409C) at address 0x42970000-0x42A58000 in Process 'NK.EXE' (0x85827AD0)
    PB Debugger Loaded 'MSCOREE3_5.DLL', no matching symbolic information found.
    8156295 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'mscoree3_5.dll' (0xBD88409C) at address 0x42970000-0x42A58000 in Process 'cgacutil.exe' (0xBD88C088)
    8156295 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'fpcrt.dll' (0xBD81A528) at address 0x40210000-0x4022E000 in Process 'cgacutil.exe' (0xBD88C088)
    8156295 PID:4c6005a TID:5a80052 !!!WARNING: Mutually dependent DLL detected: FPCRT (pMod = 0x001208b0)
    8156295 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'ws2.dll' (0xBD843280) at address 0x41220000-0x41236000 in Process 'cgacutil.exe' (0xBD88C088)
    8156295 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'ole32.dll' (0xBD857B1C) at address 0x41A20000-0x41B25000 in Process 'cgacutil.exe' (0xBD88C088)
    8156295 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'rpcrt4legacy.dll' (0xBD857C54) at address 0x41BD0000-0x41C76000 in Process 'cgacutil.exe' (0xBD88C088)
    8156295 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'lpcrt.dll' (0xBD858270) at address 0x414A0000-0x414A7000 in Process 'cgacutil.exe' (0xBD88C088)
    8156295 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'bcrypt.dll' (0xBD8458AC) at address 0x43CD0000-0x43D22000 in Process 'cgacutil.exe' (0xBD88C088)
    8156295 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'oleaut32.dll' (0xBD8598E8) at address 0x41B30000-0x41B86000 in Process 'cgacutil.exe' (0xBD88C088)
    8156295 PID:400002 TID:5a80052 Warning: you are requesting IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMTYPE, which has been deprecated.  Use IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMNAME instead.
    8156295 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'toolhelp.dll' (0xBD80FABC) at address 0x40EF0000-0x40EF7000 in Process 'cgacutil.exe' (0xBD88C088)
    8156295 PID:400002 TID:5a80052 OSAXST1: >>> Loading Module 'netcfagl3_5.dll' (0xBD8861C0) at address 0x42A60000-0x42A9E000 in Process 'NK.EXE' (0x85827AD0)
    PB Debugger Loaded 'NETCFAGL3_5.DLL', no matching symbolic information found.
    8156869 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'netcfagl3_5.dll' (0xBD8861C0) at address 0x42A60000-0x42A9E000 in Process 'cgacutil.exe' (0xBD88C088)
    8156869 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'commctrl.dll' (0xBD85A180) at address 0x40FC0000-0x4109B000 in Process 'cgacutil.exe' (0xBD88C088)
    8156869 PID:400002 TID:5a80052 Warning: you are requesting IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMTYPE, which has been deprecated.  Use IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMNAME instead.
    8156869 PID:4c6005a TID:5a80052 OSAXST1: >>> Loading Module 'aygshell.dll' (0xBD863660) at address 0x42850000-0x42869000 in Process 'cgacutil.exe' (0xBD88C088)
    8156869 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'aygshell.dll' (0xBD863660) at address 0x42850000-0x42869000 in Process 'cgacutil.exe' (0xBD88C088)
    8157005 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'toolhelp.dll' (0xBD80FABC) at address 0x40EF0000-0x40EF7000 in Process 'cgacutil.exe' (0xBD88C088)
    8157005 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'commctrl.dll' (0xBD85A180) at address 0x40FC0000-0x4109B000 in Process 'cgacutil.exe' (0xBD88C088)
    8157005 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'netcfagl3_5.dll' (0xBD8861C0) at address 0x42A60000-0x42A9E000 in Process 'cgacutil.exe' (0xBD88C088)
    8157005 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'netcfagl3_5.dll' (0xBD8861C0) at address 0x42A60000-0x42A9E000 in Process 'cgacutil.exe' (0xBD88C088)
    PB Debugger Unloaded symbols for 'NETCFAGL3_5.DLL'
    8157104 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'mscoree3_5.dll' (0xBD88409C) at address 0x42970000-0x42A58000 in Process 'cgacutil.exe' (0xBD88C088)
    8157104 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'mscoree3_5.dll' (0xBD88409C) at address 0x42970000-0x42A58000 in Process 'cgacutil.exe' (0xBD88C088)
    PB Debugger Unloaded symbols for 'MSCOREE3_5.DLL'
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'ole32.dll' (0xBD857B1C) at address 0x41A20000-0x41B25000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'coredll.dll' (0xBD80DD6C) at address 0x40010000-0x40163000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'oleaut32.dll' (0xBD8598E8) at address 0x41B30000-0x41B86000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'rpcrt4legacy.dll' (0xBD857C54) at address 0x41BD0000-0x41C76000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'bcrypt.dll' (0xBD8458AC) at address 0x43CD0000-0x43D22000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'lpcrt.dll' (0xBD858270) at address 0x414A0000-0x414A7000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'ws2.dll' (0xBD843280) at address 0x41220000-0x41236000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'fpcrt.dll' (0xBD81A528) at address 0x40210000-0x4022E000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'normalize.dll' (0xBD80F704) at address 0x401E0000-0x40200000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'locale.dll' (0xBD80F260) at address 0x40170000-0x401B1000 in Process 'cgacutil.exe' (0xBD88C088)
    8157479 PID:4c6005a TID:5a80052 OSAXST1: <<< Unloading Module 'cgacutil.exe' (0xBD88C088) at address 0x00010000-0x00018000 in Process 'cgacutil.exe' (0xBD88C088)
    PB Debugger Unloaded symbols for 'CGACUTIL.EXE'
    8157506 PID:400002 TID:f502fa ERROR! LoadLibrary on EXE!
    8157506 PID:400002 TID:f502fa ERROR! LoadLibrary on EXE!
    8157927 PID:366013e TID:f502fa OSAXST1: <<< Unloading Module 'lpcrt.dll' (0xBD858270) at address 0x414A0000-0x414A7000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8157927 PID:366013e TID:f502fa OSAXST1: <<< Unloading Module 'bcrypt.dll' (0xBD8458AC) at address 0x43CD0000-0x43D22000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8157927 PID:366013e TID:f502fa OSAXST1: <<< Unloading Module 'rpcrt4legacy.dll' (0xBD857C54) at address 0x41BD0000-0x41C76000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8157927 PID:366013e TID:f502fa OSAXST1: <<< Unloading Module 'ole32.dll' (0xBD857B1C) at address 0x41A20000-0x41B25000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8157927 PID:366013e TID:f502fa OSAXST1: <<< Unloading Module 'mscoree.dll' (0xBD8843D0) at address 0x42950000-0x42962000 in Process 'ConManClient2.exe' (0xBD857D8C)
    8157927 PID:366013e TID:f502fa OSAXST1: <<< Unloading Module 'mscoree.dll' (0xBD8843D0) at address 0x42950000-0x42962000 in Process 'ConManClient2.exe' (0xBD857D8C)
    PB Debugger Unloaded symbols for 'MSCOREE.DLL'
    8158156 PID:1860426 TID:1b20582 OSAXST1: >>> Loading Module 'ossvcs.dll' (0xBD859B24) at address 0x42C30000-0x42CA1000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 OSAXST1: >>> Loading Module 'ole32.dll' (0xBD857B1C) at address 0x41A20000-0x41B25000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 OSAXST1: >>> Loading Module 'rpcrt4legacy.dll' (0xBD857C54) at address 0x41BD0000-0x41C76000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 OSAXST1: >>> Loading Module 'lpcrt.dll' (0xBD858270) at address 0x414A0000-0x414A7000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 OSAXST1: >>> Loading Module 'bcrypt.dll' (0xBD8458AC) at address 0x43CD0000-0x43D22000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 OSAXST1: >>> Loading Module 'shlwapi.dll' (0xBD85C418) at address 0x41D40000-0x41D98000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 OSAXST1: >>> Loading Module 'oleaut32.dll' (0xBD8598E8) at address 0x41B30000-0x41B86000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 ShellReady: Wait until shell is ready: 8158186
    8158156 PID:1860426 TID:1b20582 OSAXST1: <<< Unloading Module 'lpcrt.dll' (0xBD858270) at address 0x414A0000-0x414A7000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 OSAXST1: <<< Unloading Module 'bcrypt.dll' (0xBD8458AC) at address 0x43CD0000-0x43D22000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 OSAXST1: <<< Unloading Module 'rpcrt4legacy.dll' (0xBD857C54) at address 0x41BD0000-0x41C76000 in Process 'edm2.exe' (0xBD874DFC)
    8158156 PID:1860426 TID:1b20582 OSAXST1: <<< Unloading Module 'ole32.dll' (0xBD857B1C) at address 0x41A20000-0x41B25000 in Process 'edm2.exe' (0xBD874DFC)
    8158190 PID:1860426 TID:1b20582 OSAXST1: <<< Unloading Module 'oleaut32.dll' (0xBD8598E8) at address 0x41B30000-0x41B86000 in Process 'edm2.exe' (0xBD874DFC)
    8158190 PID:1860426 TID:1b20582 OSAXST1: <<< Unloading Module 'shlwapi.dll' (0xBD85C418) at address 0x41D40000-0x41D98000 in Process 'edm2.exe' (0xBD874DFC)
    8158190 PID:1860426 TID:1b20582 OSAXST1: <<< Unloading Module 'ossvcs.dll' (0xBD859B24) at address 0x42C30000-0x42CA1000 in Process 'edm2.exe' (0xBD874DFC)
    8158703 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'coredll.dll' (0xBD80DD6C) at address 0x40010000-0x40163000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8158703 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'CTIEntryPointDummy.exe' (0xBD88C088) at address 0x00010000-0x00018000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    PB Debugger Loaded 'C:\JOSEPROJECTS\SMC\EC1000_COMPACT7\SERVER\ENTRYPOINTDUMMY\OBJ\ARMV7\RETAIL\CTIENTRYPOINTDUMMY.EXE', no matching symbolic information found.
    8159866 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'locale.dll' (0xBD80F260) at address 0x40170000-0x401B1000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8160434 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'normalize.dll' (0xBD80F704) at address 0x401E0000-0x40200000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8160434 PID:400002 TID:4590062 OSAXST1: >>> Loading Module 'mscoree.dll' (0xBD884000) at address 0x42950000-0x42962000 in Process 'NK.EXE' (0x85827AD0)
    PB Debugger Loaded 'MSCOREE.DLL', no matching symbolic information found.
    8161062 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'mscoree.dll' (0xBD884000) at address 0x42950000-0x42962000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8161062 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'ole32.dll' (0xBD857B1C) at address 0x41A20000-0x41B25000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8161062 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'rpcrt4legacy.dll' (0xBD857C54) at address 0x41BD0000-0x41C76000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8161062 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'lpcrt.dll' (0xBD858270) at address 0x414A0000-0x414A7000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8161062 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'bcrypt.dll' (0xBD8458AC) at address 0x43CD0000-0x43D22000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8161062 PID:4560062 TID:4590062 CePerf.dll is absent - performance data will not be recorded
    8161062 PID:400002 TID:4590062 OSAXST1: >>> Loading Module 'mscoree3_5.dll' (0xBD885F64) at address 0x42970000-0x42A58000 in Process 'NK.EXE' (0x85827AD0)
    PB Debugger Loaded 'MSCOREE3_5.DLL', no matching symbolic information found.
    8161792 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'mscoree3_5.dll' (0xBD885F64) at address 0x42970000-0x42A58000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8161792 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'fpcrt.dll' (0xBD81A528) at address 0x40210000-0x4022E000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8161792 PID:4560062 TID:4590062 !!!WARNING: Mutually dependent DLL detected: FPCRT (pMod = 0x00031060)
    8161792 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'ws2.dll' (0xBD843280) at address 0x41220000-0x41236000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8161792 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'oleaut32.dll' (0xBD8598E8) at address 0x41B30000-0x41B86000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8161792 PID:400002 TID:4590062 Warning: you are requesting IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMTYPE, which has been deprecated.  Use IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMNAME instead.
    8161792 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'toolhelp.dll' (0xBD80FABC) at address 0x40EF0000-0x40EF7000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8162125 PID:400002 TID:4590062 OSAXST1: >>> Loading Module 'netcfagl3_5.dll' (0xBD886D0C) at address 0x42A60000-0x42A9E000 in Process 'NK.EXE' (0x85827AD0)
    PB Debugger Loaded 'NETCFAGL3_5.DLL', no matching symbolic information found.
    8162755 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'netcfagl3_5.dll' (0xBD886D0C) at address 0x42A60000-0x42A9E000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8162756 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'commctrl.dll' (0xBD85A180) at address 0x40FC0000-0x4109B000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8162756 PID:400002 TID:4590062 Warning: you are requesting IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMTYPE, which has been deprecated.  Use IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMNAME instead.
    8162756 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'aygshell.dll' (0xBD863660) at address 0x42850000-0x42869000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8162756 PID:4560062 TID:4590062 OSAXST1: <<< Unloading Module 'aygshell.dll' (0xBD863660) at address 0x42850000-0x42869000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8162778 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'edbgtl.dll' (0xBD858438) at address 0x43D30000-0x43D45000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)
    8162778 PID:4560062 TID:4590062 OSAXST1: >>> Loading Module 'tlkitlc.dll' (0xBD8740C0) at address 0x43D50000-0x43D58000 in Process 'CTIEntryPointDummy.exe' (0xBD88C088)


    Wednesday, March 13, 2013 5:54 PM
  • I meant registry settings described here:

    http://blogs.msdn.com/b/davidklinems/archive/2005/05/24/421566.aspx

    If you launch/deploy via VS that should not be needed though. 

    I would suggest getting rid of PB for managed part and using VS only. You can try it with emulator just to verify if pipeline is operational.


    This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, March 13, 2013 9:42 PM
  • Oh OK I did create the registry key mention on the link but still not hitting breakpoints and yes any way I do launch/deploy from VS, so I probably should set the key back to zero.  The only reason I am also using PB is so that I can download the O/S image which is currently not in the device. I guess I will try the Emulator next.

    I am not using an image SDK (yet) on VS because I assumed it is not needed to develop Managed code and I am connecting to (auto)Ether. Am I correct on this asumption?

    Wednesday, March 13, 2013 10:16 PM
  • I created an SDK from my O/S image, installed it and then created a simple c# project with it. Then after adding the target IP address and then trying to connect I get "Connection failed. ActiveSync bootstrap initialization failed" If I go back to my original C# projects using (auto)Ether then I connect fine (but still unable to debug). Any ideas why I get this error?

    I am still working on getting my O/S image to boot from Flash instead of a Bootme  to PB so that I can eliminate PB from the equation as you suggested.

    Thursday, March 14, 2013 12:52 AM
  • Your assumption is generally correct - SDK generated by PB is for native development only. 

    Since it's a custom image it's possible something managed debugger needs is missing from the OS image.


    This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, March 14, 2013 1:04 AM
  • Hi Ilya,

    Other posts in your forum mention that the breakpoints problem was caused by a mismatch between .NETCF installed in your development PC vs the one in your Compact 7 Device. But they refer to the 2.0 versions. Could there be more then one .NETCF 3.5 versions and how do I check if there is a mismatch?

    Thursday, March 14, 2013 5:58 PM
  • There are number of QFEs for NETCF 3.5, technically they are different versions. However QFEs generally don't change any public APIs so it's unlikely to be an issue.

    Have you tried stepping into the code by the way (F11 instead of F5).


    This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, March 14, 2013 7:48 PM
  • F11 caused VS to try and launch all my C# projects at once instead of just launching the one that is selected and when I said no to all other projects except the HelloWorld one it seems to hang VS.

    Running cgacutil.exe on the device shows its .NETCF ver is 3.5.10181.0 while on my development PC under "Add or remove programs" it says .NETCF ver is 3.5.7282.

    A new thing I noticed on my O/S Catalog is that ActiveSync was selected. So I think this means I have both KITL and ActiveSync enabled at the same time on my Device. Could this be the problem? I rebuilded the image w/o ActiveSync to try. But it may be worst now as VS seems to hang after deployment is done and never gets to load the VS debugger. Then I need to kill it w/ task manager.  Is there some setting in VS that may be telling it to use ActiveSync instead of using KITL?

    Thursday, March 14, 2013 11:10 PM
  • That is strange... Perhaps your VS has different key mappings. I meant "Step into the project" which basically launches the app and stops at first statement.

    Yes, you have one of the QFEs. That should not be a problem.

    AS is a separate application, it should not matter if you have both KITL and AS. For managed debugging VS is using AS by default. I don't recall if KITL is even supported for managed debugging, I would say it's not.

    Other way to debug is via TCP connection as described here:

    http://community.opennetcf.com/articles/cf/archive/2007/08/31/debugging-without-activesync.aspx

    Keep in mind I never worked with CE 7, so I may be wrong. I'd say call official support on that.


    This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, March 14, 2013 11:35 PM
  • The steps on your link is what I tried when I added the SDK an created a new C# test project. W/O the ActiveSync included in my O/S image, the conection via VS is not working as I get "Connection failed. ActiveSync bootstrap initialization failed".

    so I think I will put it back specially since you say Managed debugging needs it.

    Just to clarify, there seems to be no need to run CeDebugSetup.exe with VS2008 because every time I try to connect I can see it launching Conmanclient2.exe and CMaccept.exe inside the target. (I hope it is picking the right copies of them from my PC...) When ever I ran any of the PB RemoteTools such as, File Viewer, it also launches these executable in the target.

    I just dont know what I could possibly be missing


    Friday, March 15, 2013 12:11 AM
  • Actually I am now looking at the directories inside "C:\Program Files (x86)\Common Files\microsoft shared\CoreCon\1.0\Target\wce400" and I see that the files in subdir \armv4 are newer dates then the ones in dir \armv7 ??? And I think remember when asked at some point by VS2008 for the location of these files I selected \armv7 because that is the arm version I have on my device. If I can figure out how to tell VS to use a different dir for these files I will see if it works then...

    Friday, March 15, 2013 12:58 AM
  • Hi Ilya,

    Last week you had sugested I  get rid of PB for managed part and using VS only. I take this to mean that I load my O/S image into the device and boot it from there (instead of via PB which I was doing). I am trying this but dont think it is booting correctly. Will my image boot if it includes KITL? should I create an image w/o KITL and use something like SVCStart to start both cerdisp.exe, for remote display and correct version of ConmanClient2.exe? Anything else I need to get debug working with VS?

    Thanks/Jose

    Tuesday, March 19, 2013 10:12 PM
  • I think I may know the cause of my problem but dont know how to fix it. I have this two subdirectories:

    C:\Program Files (x86)\Common Files\microsoft shared\CoreCon\5.01\...

    and

    C:\Program Files (x86)\Common Files\microsoft shared\CoreCon\1.0\...

    If I rename the 1.0 dir then VS2008 will not care but if I rename the 5.01 dir then VS2008 will get a popup error (package 'vscoreconpkg package' has failed to load) So it seems that VS is using some files in 5.01. But when I look at the ConManClient2.exe used in the Compact7 image they come from the 1.0 dir. So I suspect there is a comflict of CoreCon versions between my device and VS. The thing is that I dont know how to get VS2008 to switch and use what ever files it needs from CoreCon 1.0. I also dont know where CoreCon 5.01 came from and what it is used for? (possible something related to Windows Mobile?)  I know my PC also has VS2010 installed and it may have come from there

    Is anyone familiar with this problem and how to fix it? else can someone guide me to the appropriate forum for this Compact7 debug issue?

    Wednesday, March 20, 2013 5:48 PM
  • I'm not sure what CoreCon 5.01 is, as far as I recall it should be 1.0. 

    Yes, this mismatch would probably do it. You can probably try creating a copy of 5.01 just in case and then creating 5.01 folder with 1.0 files in it.

    VS 2010 does not have device development so it's not likely.


    This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, March 20, 2013 10:55 PM