Windows Mobile 2003 Second Edition Question

[Nancy Kafer]

I have a new device that is running Windows Mobile 2003 Second Edition. When
I try to run a smart device application that I created on this device I am
having problems (this doesn't happen on just a straight Pocket PC 2002
device). I have tracked the problem to a problem with the SYSTEM_SR_enu.cab
file not being installed properly.

My research has told me that this CAB file is related to the .NET Compact
Framework. I also discovered that Windows Mobile 2003 Second Edition may not
be supported with the current version of the .NET Compact Framework. Is this
true? If so how can I get around this problem?

Thanks.

 

[Daniel Moth]

No.

Pocket PC 2003 is supported by all versions of CF. The latest current
version is CF 1.0 SP3 and the one in Beta is CF 2.0

System.SR is not part of the CF itself but serves as an aid for developers
when they get runtime exceptions while debugging. It contains the exception
strings (available in several languages).

"Having problems" and "tracked down" are too vague. Describe your problem in
full if you need assistance solving it.

Cheers
Daniel

 

[Nancy Kafer]

I have one page that is a calculator page. The page accepts various amounts
and other parameters to be used in the calculation routines I have in a
separate dll (added to my project as a reference). One of these fields is a
drop-down box that contains state codes that are read from a SQL CE
database. This drop-down is working fine. I enter the rest of the values and
press the "Calculate" button. The program throws an exception when calling a
calculation routine that is contained in the referenced dll. This only
happens on the Windows Mobile 2003 SE device....my Pocket PC 2002 device
works fine.

Based on the error message "Device installation of 'SYSTEM_SR_enu.cab' is
not completed. I am thinking that something didn't install properly.

What could be causing my problem.

 

[Daniel Moth]

What is probably happening is that you are getting another exception and
when it tries to retrieve the exception text from SR, it fails and then you
see the exception you describe.

As for your bad SR installation, all I can suggest is to hard reset.

You said you have another device where it works. Compare the CF version on
both devices. Update both devices with SP3 and let us know the new results:
http://wiki.opennetcf.org/ow.asp?CompactFrameworkFAQ/DeterminingVersion

One of the common breaking changes between an older CF version and a newer
one is using desktop assemblies on the device. This is not supported and
leads to TypeLoadExceptions:
http://groups-beta.google.com/group...eption+SP2&qt_g=1&searchnow=Search+this+group

Good luck.

Cheers
Daniel

 

[Alex Feinman [MVP]]

And the exception is...?
Is it so hard to provide relevant information?

What is the type of the exception? What is the lline that throws it? Is it
happening in your own component? Can you get there in a debugger?

By the way, System.SR has nothing to do with you problem.

 

[Nancy Kafer]

Thanks for all of the help. I was able to figure out my problem. Turns out
it was related to a path in my dll. I'm not sure why this worked on the
Pocket PC 2002 device because it shouldn't have.