"Assembly of Ressource not found"

[Guest]

Hello NG!

I've created the CAB-files for my CF-app with the wizard. Now I want to test
it on two devices:

(1) iPaq 3850, ARM SA1110, PPC2002
(2) Medion, Intel PXA250, PPC2002

For both I've taken "..._PPC.ARM.CAB".

On device (1) everything works fine, but on device (2) there apears an error
"The Assembly of the Ressource couldn't be found".

Anyone knowing what's the problem? Is it a problem of the wrong CAB-file?
When do I have to take "..._PPC.ARMV4.CAB"?

The project consists of one Main-Project that references to a bought
component and to some own components (dll's).

Thanks, D.Barisch

 

[Alex Feinman [MVP]]

At which point do you get the error? Installing or running the app?
The cabs produced by Visual Studio are identical except of a small unmanaged
DLL used to detect framework presence on the device. The proper CAB for
PPC2002 deployment is ..._PPC.ARM

 

[Guest]

At which point do you get the error? Installing or running the app?
Runtime

I have new Row of a DataTable with a primary key consisting of 2 columns. If
I do not enter a value for both columns and try to add the row to the table,
then a System.Data.DataException is thrown. On one Device there appears the
expected error-message ("...InvalidConstraint...") but on the other one ex
has the message(but still thrown as DataException!)

Any suggestions?

Thanks, D.Barisch

 

[Alex Feinman [MVP]]

That likely refers to the lack os System.SR.DLL which contains error
messages. This is normal - System.SR.DLL is not rediustributable.

 

[Guest]

That likely refers to the lack os System.SR.DLL which contains error

messages. This is normal - System.SR.DLL is not rediustributable.

What does that mean to me? Do I have to distribute that file 'manual'? Why
does it work on one device, but not on an other one?

Thank you for your help!

D.Barisch

 

[Alex Feinman [MVP]]

This assembly is installed by VStudio during deployment. It is not a part of
CF redistributable. The idea is that your user does not see the exception
details - consider it debug information. The exception message you refer to
is for you - to help you while you are developing your application

 

[Guest]

This assembly is installed by VStudio during deployment. It is not a part
of

CF redistributable. The idea is that your user does not see the exception
details - consider it debug information. The exception message you refer to
is for you - to help you while you are developing your application

So I should use own Error-Messages instead of calling ex.Message? But I
thougth it is practical to catch a System.Data.DataException and then simply
write the message which in my opinion in most cases is user-friendly.
Instead I have to catch every type of exception, right? Is there soething
like a list, where I can see, which exception-messages were not a part of CF
redistributable?

Thanks, D.Barisch

 

[Ilya Tumanov [MS]]

Daniel,

Have you ever seen error messages like "Unknown internal error" or "Error
0x12345" or even descriptive ones like "Unable to reset bit 15 in flux
capacitor port 0x99"?
I'm sure you have. How these error messages makes you feel? Frustrated, may
be even angry, right?
This is because some developer was sure system error messages are user
friendly enough.

Don't do that. Catch all exceptions and replace them with message making
sense to your customers.
Or, even better, fix the problem and retry. My be you can recommend some
fix like "Run database repair tool located in...".

I'm sure something like this "The relation is not parented to the table to
which this DataView points" will help you.
Are you sure your customer knows what are relations, tables and DataView?
Why it's not parented and how to fix it?
I don't think so. Be nice to your customers and do not rely on system
messages.
You'll be rewarded by fewer support calls and better relationship.

Best regards,

Ilya



This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

From: <Daniel Barisch>
References: <[email protected]>

<[email protected]>
<#[email protected]>
<[email protected]>