problem with casting byte array to ascii

Question

1.00/5 (1 vote)

See more:

i am using string s=Encoding.ASCII.GetString(bytes) output shoul be 111187686557 but it gives
111187686557\0\0\0\0\ etc many times \0 plz help me?
byte array shows 10 value and other values are 0 but while converting to the string it takes 0 as \0 help me

Posted 11-Feb-14 20:04pm

Member 9027346

Updated 11-Feb-14 22:22pm

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-02-11T20:13:00

Solution 1

Why do you think if should give this string? If it does not, the content stored in your bytes is really not what you expected encoded as ASCII.

It could be anything: 1) your original string could be encoded not as ASCII, 2) your original string could really contain many zeroes; this is not that silly C-style null-terminated string; in .NET strings, null is valid; 3) it could be anything else. If you had to serialize some string, deserialize it and compare the result of this round-trip operation, it would be a different story. If you show the code making bytes from your string, we can consider it.

—SA

Posted 11-Feb-14 20:13pm

Sergey Alexandrovich Kryukov

Comments

Garth J Lancaster 12-Feb-14 2:18am

beats my first comment Sergey :-) - I said use s.Trim() d'oh forgetting the input was byte[] .. sigh

Sergey Alexandrovich Kryukov 12-Feb-14 2:26am

Trim is irrelevant. By the way, Trim() without parameters should not trim those nulls (surprise?). When you serialize the string if becomes array of byte. Deserialize it with the same encoding, and it will give the same string. No matter what it was. But it the character repertoire of the encoding (ASCII! generally, should not be used with .NET), it won't be the case. Only UTFs guarantee correct round trip.
—SA

Garth J Lancaster · Answer 2 · 2014-02-11T20:16:00

Solution 2

you do realise that

s=Encoding.ASCII.GetString(bytes)

can also be specified

s=Encoding.ASCII.GetString(bytes, offset, length)

offset is likely 0, as per SA's comments, its up to you to determine the correct length

'g'

Posted 11-Feb-14 20:16pm

Garth J Lancaster

Comments

Sergey Alexandrovich Kryukov 12-Feb-14 2:28am

Please see my comment to your comment to my answer. ASCII does not guarantee correct round trip. Further discussion is pretty much useless, unless OP clearly shows how bytes were obtained.
—SA