[Windows Phone 7 Development and Hacking] Martin7Pro:
Update 1st issue:

On Second PC:

1st (better) device - debugger works (shows trace output) and sometimes stops automatically after application finishing too:

... There is 20s delay here

Load module: Pok4.exe

Load module: coredll.dll.0405.MUI

Load module: LPCRT.dll

Load module: RPCRT4LEGACY.dll

Load module: OLEAUT32.dll

Load module: ole32.dll

Load module: FPCRT.dll

Load module: coredll.dll

Toto je zacatek ... message from AtlTrace

Load module: AYGSHELL.dll

Load module: eventsnd.dll

Load module: waveapic.dll

Load module: ossvcs.dll

Load module: shlwapi.dll

Load module: phone.dll

Load module: shcore.dll

Load module: PACMANCLIENT.dll

Load module: EMCLIENT.dll

Load module: ZTrace.dll

Load module: ril.dll

The thread 0x1923000e has exited with code 16 (0x10).

... There I must stop PC debugger manually sometimes, or kill edm2p.exe on device, Pok4.xe is unkillable sometime. But sometimes debugger stops itself.

The program '[0x18DA000E] Pok4.exe' has exited with code 1067 (0x42b).

2nd (worse) device - debugger works, but does not show trace output and does not stop automatically after application finishing:

... There is 30s delay here (only first time, may be it is devivice debugger starting pause, debugger is not killed automatically)

Load module: Pok4.exe

Load module: coredll.dll.0405.MUI

Load module: RPCRT4LEGACY.dll

Load module: OLEAUT32.dll

Load module: ole32.dll

Load module: FPCRT.dll

Load module: coredll.dll

Load module: AYGSHELL.dll

Load module: ossvcs.dll

Load module: waveapic.dll

Load module: shlwapi.dll

Load module: shcore.dll

... There I must stop PC debugger manually everytime here

Do you somebody understand output difference? Application project, PC and VS is the same, device is changed (and WPConnect called) only.

LPCRT.dll miss in second output. This seems second device has no registered ATL COM proxy dll (I found something here http://cboard.cprogramming.com/cplu...-proxy-dll-difficulties-windows-ce-5-0-a.html). Do you understand COM somebody better then me?

Edit: After any minutes, WITHOUT any changing, second (worst) device begin better behaviour - debugger is closed corretly and immediatelly:

Load module: Pok4.exe

Load module: coredll.dll.0405.MUI

Load module: RPCRT4LEGACY.dll

Load module: OLEAUT32.dll

Load module: ole32.dll

Load module: FPCRT.dll

Load module: coredll.dll

Load module: AYGSHELL.dll

Load module: ossvcs.dll

Load module: waveapic.dll

Load module: shlwapi.dll

Load module: shcore.dll

The thread 0x1ae4034e has exited with code 0 (0x0).

The program '[0x1B1D036A] Pok4.exe' has exited with code 0 (0x0).

Now this behaviour is similar to my first PC yasterday. I do not understand it totally. On first device still AtlTrace works and thread has exited with code 16. There is debugger problem probably to handle application exception.

Application Pok4 contains this code only:

extern "C" int WINAPI _tWinMain(HINSTANCE /*hInstance*/, HINSTANCE /*hPrevInstance*/,

LPTSTR /*lpCmdLine*/, int nShowCmd)

{

ATLTRACE2(L"Toto je zacatek\n");

MessageBox(NULL, L"Po začátku", L"_tWinMain", MB_OK);

int i = 0;

return 0;

}

It looks like ATL COM proxy generates Trace output on first device, but it generates also undebuggable exception on it (EDIT: Probably not true, see next post!). But this behaviour is sometimes very random.

When I change ATLTRACE2 to OutputDebugString, behaviour of both devices is exactly the same as with ATLTRACE2..