Hello Paul,
We got now the latest QFEs (040810, 040811, 040813) but it's still the same.
(also after deploying and installing the CF via Visual Studio the Testapp
doesn't run)
What's your further suggestions?
Michael
"Paul G. Tobey [eMVP]" wrote:
> And the QFEs? It appears to me that there is something wrong during the
> initial compilation of the program, causing the run-time to exit suddenly.
> There have been QFEs which prevented .NET CF apps from running on 4.2
> devices. You have to get all of the latest updates to assure that you are
> in a position to build a working OS in that area.
>
> Paul T.
>
> "Michael" <(E-Mail Removed)> wrote in message
> news:FB1FA2AF-F174-4568-BE6B-(E-Mail Removed)...
> > Hello Paul,
> >
> > by run the application manually the Platformbuilder shows a window (Enter
> > the path of the app...) and the enclosed debug messages (from
> > Platformbuilder):
> >
> > 370376 PID:61d21a06 TID:61f1a4da 0x81d55d4c: >>> Loading module
> > mscoree.dll
> > at address 0x03700000-0x03708000 (RW data at 0x01F7E000-0x01F7E124)
> > Loaded
> > 'C:\WINCE420\PUBLIC\OPAL_PLATTFORM_STANDARD\RELDIR\OPAL_BSPDEBUG\MSCOREE.DLL',
> > no matching symbolic information found.
> > 370404 PID:61d21a06 TID:61f1a4da 0x81d55d4c: >>> Loading module
> > SmartDeviceApplication4.exe at address 0x10010000-0x10018000
> > Loaded 'SmartDeviceApplication4.exe', no matching symbolic information
> > found.
> > 403981 PID:61d21a06 TID:61f1a4da 0x81d55d4c: >>> Loading module
> > wininet.dll
> > at address 0x03490000-0x03577000 (RW data at 0x01F6E000-0x01F71838)
> > Loaded symbols for
> > 'C:\WINCE420\PUBLIC\OPAL_PLATTFORM_STANDARD\RELDIR\OPAL_BSPDEBUG\WININET.DLL'
> > 404038 PID:61d21a06 TID:61f1a4da 0x81d55d4c: >>> Loading module
> > mscoree1_0.dll at address 0x01DD0000-0x01E5D000
> > Loaded
> > 'C:\WINCE420\PUBLIC\OPAL_PLATTFORM_STANDARD\RELDIR\OPAL_BSPDEBUG\MSCOREE1_0.DLL',
> > no matching symbolic information found.
> > 404113 PID:61d21a06 TID:61f1a4da 0x81d55d4c: Process
> > SmartDeviceApplication4.exe loaded Module wininet.dll without freeing it
> > before process exit
> > 404120 PID:61d21a06 TID:61f1a4da 0x81d55d4c: Process
> > SmartDeviceApplication4.exe loaded Module mscoree1_0.dll without freeing
> > it
> > before process exit
> > 404124 PID:61d21a06 TID:61f1a4da 0x81d55d4c: Winsock: WSAStartup and
> > WSACleanup have not been called--potential memory leak!
> > 404145 PID:61d21a06 TID:61f1a4da 0x81d55d4c: <<< Unloading module
> > wininet.dll at address 0x03490000-0x03577000 (RW data at
> > 0x01F6E000-0x01F71838)
> > Unloaded symbols for
> > 'C:\WINCE420\PUBLIC\OPAL_PLATTFORM_STANDARD\RELDIR\OPAL_BSPDEBUG\WININET.DLL'
> > 404162 PID:61d21a06 TID:61f1a4da 0x81d55d4c: <<< Unloading module
> > mscoree1_0.dll at address 0x01DD0000-0x01E5D000
> > Unloaded symbols for
> > 'C:\WINCE420\PUBLIC\OPAL_PLATTFORM_STANDARD\RELDIR\OPAL_BSPDEBUG\MSCOREE1_0.DLL'
> > 404180 PID:a1fe5262 TID:61f1a4da 0x81d55d4c: WARNING: Cleaned up 1 leaked
> > registry handles for process 0x61D21A06
> > 404194 PID:61d21a06 TID:61f1a4da 0x81d55d4c: <<< Unloading module
> > SmartDeviceApplication4.exe at address 0x10010000-0x10018000
> > Unloaded symbols for 'SmartDeviceApplication4.exe'
> > 404208 PID:61d21a06 TID:61f1a4da 0x81d55d4c: <<< Unloading module
> > mscoree.dll at address 0x03700000-0x03708000 (RW data at
> > 0x01F7E000-0x01F7E124)
> > Unloaded symbols for
> > 'C:\WINCE420\PUBLIC\OPAL_PLATTFORM_STANDARD\RELDIR\OPAL_BSPDEBUG\MSCOREE.DLL'
> >
> > Thanks in advance, Michael
> > ---------------------------------------------------------------
> >
> > "Paul G. Tobey [eMVP]" wrote:
> >
> >> Make sure that you have installed all of the latest WinCE 4.2 QFEs from
> >> the
> >> Microsoft download site. Enable the serial debug messages from a debug
> >> build of your platform and capture them while trying to run the
> >> application
> >> manually (leave VS.NET out of it). Let us know what the serial debug
> >> messages show.
> >>
> >> Paul T.
> >>
> >> "Michael" <(E-Mail Removed)> wrote in message
> >> news:C616CEB4-A6AE-48D8-AF3A-(E-Mail Removed)...
> >> > Hello,
> >> >
> >> > we have aproblem with VS .NET 2003, C#-App and our Device with a Win CE
> >> > image and included Compact Framework (Platformbuilder 4.2 with all
> >> > QFEs)
> >> >
> >> > VS .NET builds and deploys the C#-Testapp, says launching
> >> > application, but nothing happens. Also manually starting of the app on
> >> > the
> >> > device does'nt work.
> >> >
> >> > How can we determine that the .NET Compact Framework is working?
> >> >
> >> > By testing with the Emulator we see a Compact Framework folder in the
> >> > folder
> >> > Program Files but on our device we doesn't see this folder. Is this a
> >> > sign
> >> > for the inactive Compact Framework?
> >> >
> >> > Thanks in advance,
> >> >
> >> > Michael
> >>
> >>
> >>
>
>
>
|
Similar Threads
