BitConvert.ToString(0 Bug

[Opa1]

using BitConverter.ToString() in Compact Framework has some bugs.

The resulting hex string does not have a consistent format for each
byte converted from the input byte array.

for example:
Byte array with values,
(9,0,0,0,115,105,103,110,97,116,117,114,101,224,0,0,0,51,0,0,0,1)

result in,

"9-00-00-00-73-69-67-6E-61-74-75-72-65-E0-00-00-00-33-00-00-00-1"

should be,

"09-00-00-00-73-69-67-6E-61-74-75-72-65-E0-00-00-00-33-00-00-00-01"

I read some where that it has been fixed. I have .NET 1.1 Version
1.1.4322.
Is there a new update.

Does someone have a workaround function?

 

[Chris Tacke, eMVP]

You don't have 1.1 on the device. Have you applied a service pack to the
device?

 

[Peter Foot [MVP]]

There isn't a v1.1 of the Compact Framework. You can follow these
instructions to determine the version installed on the device:-
http://msdn.microsoft.com/mobility/prodtechinfo/devtools/netcf/FAQ/default.aspx#1.26

Peter

 

[Opa Campo]

.NET Compact Framework Versioin 1.02268.00
Can I update just the compact framework without
affection my normal .NET framework?

Do you know if an update will fix the BitConverter.ToString
bug?

Thanks

 

[Jon Skeet [C# MVP]]

using BitConverter.ToString() in Compact Framework has some bugs.

Please see my response in the C# newsgroup. It would be nice if you
wouldn't multi-post in future - doing so splits up the discussion,
exactly as it has done in this case.

 

[Opa Campo]

I applied SP2, but I don't think any files are being copied to the
emulator. I still show version 1.02268.00.
when running cgacutil.exe on the emulator.

Shouldn't I see the SP2 in the version somewhere?