Re: Problem running .NET CF 1.0 apps on CE 4.2 Core

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I have tried it with an app that prints to stdout when no command line args
are passed, I have also tried with a simple windows form that does nothing.
I am using standard shell without the "AYGShell API Set". the image does
have .NET CF included and it is automatically including the "OS Dependencies
for .NET Compact Framework 1.0"

I am considering going through a manual process of adding one element of the
SDK at a time to the build by hand until the CF works at this stage.

"Paul G. Tobey [eMVP]" wrote:

> OK, that looks to me like something in the startup code for the managed code
> execution environment is dieing. Try this with a simple Hello, World
> application that does *nothing* that might cause any problems. Just create
> the new app in VS, add an Exit button or a static text control with some
> message in it to the form, and try that.
>
> Do you have the .NET CF in the OS? That should automatically include the OS
> Dependencies for it, but you might forcibly add that catalog item, too. You
> *are* running a full GWES and Window Manager OS configuration? What shell
> are you using?
>
> Paul T.
>
> "dice" <dice@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:08EE62E8-344E-4645-BDC6-0847F774BD7E@xxxxxxxxxxxxxxxx
> > The image I am using is not a headless device - am runing the "Windows
> > XP-like Sample Skin". Debug is below - it does not help me at all but
> > maybe
> > someone else can spot something.
> >
> > 0x83bc5800: FATFS!FAT_GetFileAttributesW(\LMemDebug.DLL) returned
> > 0xffffffff
> > (2) [len=81]
> > 0x83bc5800: FATFS!FAT_CreateFileW(\LMemDebug.DLL) returned 0x0 (2)
> > [len=66]
> > 0x83bc5800: FATFS!FAT_GetFileAttributesW(\LMemDebug.DLL.dll) returned
> > 0xffffffff (2) [len=84]
> > 0x83bc5800: FATFS!FAT_CreateFileW(\LMemDebug.DLL.dll) returned 0x0 (2)
> > [len=70]
> > 0x83bc5800: FATFS!FAT_GetFileAttributesW(\mscoree.dll) returned 0xffffffff
> > (2) [len=78]
> > 0x83bc5800: FATFS!FAT_CreateFileW(\mscoree.dll) returned 0x0 (2) [len=64]
> > 0x83bc5800: >>> Loading module mscoree.dll at address
> > 0x033E0000-0x033E6000
> > (RW data at 0x01F09000-0x01F09124)<CR> [len=111]
> > 0x83bc5800: >>> Loading module filesplitter.exe at address
> > 0x14010000-0x14018000<CR> [len=81]
> > 0x83bc5800: >>> Loading module mscoree1_0.dll at address
> > 0x03390000-0x033DF000 (RW data at 0x01F05000-0x01F07FE0)<CR> [len=114]
> > 0x83bc5800: Process filesplitter.exe loaded Module mscoree1_0.dll without
> > freeing it before process exit<CR> [len=105]
> > 0x83bc5800: Winsock: WSAStartup and WSACleanup have not been
> > called--potential memory leak!<CR> [len=92]
> > 0x83bc5800: <<< Unloading module mscoree1_0.dll at address
> > 0x03390000-0x033DF000 (RW data at 0x01F05000-0x01F07FE0)<CR> [len=116]
> > 0x83bc5800: Process filesplitter.exe loaded Module ole32.dll without
> > freeing
> > it before process exit<CR> [len=100]
> > 0x83bc5800: WARNING: Cleaned up 1 leaked registry handles for process
> > 0x03DD5A0A<CR> [len=81]
> > 0x83bc5800: <<< Unloading module filesplitter.exe at address
> > 0x14010000-0x14018000<CR> [len=83]
> > 0x83bc5800: <<< Unloading module mscoree.dll at address
> > 0x033E0000-0x033E6000 (RW data at 0x01F09000-0x01F09124)<CR> [len=113]
> >
>
>
>
.

Quantcast