Hey Robert...I googled the exception eventtype you listed -
"WinCE50lbException" - found another thread discussing the exact
issue with running 1.0 apps on 6.1 devices. Last entry recommends
uninstalling the install of the 1.1 runtime and letting the native 2.0
CF runtime handle it. Seems like a long shot, but it's worth a try,
right?
Also, note that VS 2010 does not have support for developing to WM6.x
devices, phone Phone 7 as I understand it. You'd need to go with VS
2005 or 2008 if you decided to upgrade to CF 2.0 or 3.5.
I have an application that I developed in Visual Studio 2003 which
uses compact framework 1.1
It has been running happily for 5 or 6 years on Symbol MC9000 rugged
handhelds,
and the company have just got a test unit Intermec CK3 with Windows
Mobile 6.1
As part of the install I include the cabs:
netcf.all.wce4.ARMV4 12/11/2003
sql.wce4.armv4 19/10/2002
and my application cab file.
When I run the program it comes up with the sorry there was an error,
and the details don't appear to make a lot of sense.
If I uninstall the compact framework, the program will run, make the
SQL Server database connection, save data etc, but not all the
functionality works.
Is there a later version of the compact framework that needs to be
installed, or is it just not compatible with WM 6 ?
We only have Visual Studio 2008 standard, so I can't develop for
mobile devices, and we don't really want to upgrade to 2010
Any help or advice would be appreciated.
Robert
Those errors that don't make a lot of sense might actually be helpful
to someone - could you post them?
We are using similar hardware. Try installing the following cab files
instead:
netcf.all.wce4.ARMV4I 11/15/2004
sqlce20.ppc.wce5.armv4i 7/29/2005
sqlce20.dev.ppc.wce5.armv4i 7/29/2005 (this will give you more helpful
error messages for SQL exceptions)
Good luck!
-Brian- Hide quoted text -
- Show quoted text -
Thanks for the reply Brian
The error seems to be associated with the compact framework.
I downloaded SP3 and installed netcf.all.wce4.ARMV4i 11/15/2004
but then starting my app threw an error again, and it doesn't appear
too helpful
Error Reporting
Bucket Parameters
==============================
EvntType: WinCE50lbExceptio
AppName : CarsPlusPPC.exe
AppVer : 3.0.0.0
AppStamp: 4c58flll
Offset :1ca2bebc
......
Exception Information
===========================
API Cur Process: 0x00000000
API Cur Thread : 0x00000000
API Own Process: 0x00000000
Info Flags : 0x000000000
Current Process: 0x8681BE06
Faulting Thread: 0x86B546A2
Owner Process : 0x8681BE06
Code : 0xC0000005
Flags : 0x00000000
Record : 0x00000000
Address : 0x00A2BEBC
Parameters: 2
Param[ 0] : 0x00000000
Param[1 ] : 0x00A2BEBC
Sytem Information
=============================
OS Version : 5.2.20758.3
LCID : 1033
CPU Architec: 5
CPU Type : 2577
CPU Level : 4
CPU Revision: 7
Machine : 0x01C2
OEM String : Intermec CK3
Platform Ver: 4.0
Module List
===============
too much to type out
hope that info is enough, tis all greek to me.
Cheers
Robert- Hide quoted text -
I looks like the behaviour that I observed, removing 1.1 SP3 made the
error disappear,
but I also appear to have lost functionality.
Part of the app calls up a new form with a modified Sub New, so I have
access to which
form popped up the new form so I can send some data back.
Private callingForm As frmVehicleDesc
Private Const strModName = "frmVehicleExtras"
#Region " Windows Form Designer generated code "
Public Sub New(ByVal newCallingForm As frmVehicleDesc)
MyBase.New()
'This call is required by the Windows Form Designer.
InitializeComponent()
'Add any initialization after the InitializeComponent() call
callingForm = newCallingForm
End Sub
This part of the code when pop up form is to be closed:
callingForm.mvextras.Text = strExtras & " "
Me.Hide()
'callingForm.cmdSave.Focus()
callingForm.TabControl1.SelectedIndex = 6
callingForm.mvtest1.Focus()
Under CF 2.0 the form does not close and the prgram gets stuck.
Thanks again for your help, bit of lag between responses because I am
on the
other side of the world in Australia.
Robert
