At this point most people will be thinking "Ah ill post this..:"
byte[] dataB= System.Text.Encoding.ASCII.GetBytes(data);
However.. the problem I have is i need the exact value of the bytes with no encoding just the pure value for each byte. For example if the value of the string is (0xFF32) i want it to convert it too {255,50}. he reason for this is I have a file format I am attempting to read which stores int's as bytes saves them and then reads them when the program opens.
This is what I have so far:
...
dialog.InitialDirectory =
Environment.GetFolderPath(System.Environment.SpecialFolder.Desktop) +
"/Test";
dialog.Title="Open File";
if (dialog.ShowDialog(this) == DialogResult.OK)
{
StreamReader reader = new StreamReader(dialog.FileName);
string data = reader.ReadToEnd();
reader.Close();
byte[] fileC = System.Text.Encoding.ASCII.GetBytes(data);
File_Read(dialog.FileName,fileC);
}
...
So when I try and read the file it converts the file convents of say 0xFF into 0x3F because 0xFF is greater then 127 and 0x3F is a ?.
Sorry if i seem a bit confusing :)
Thanks, Michael
Use a BinaryReader.
Why convert from string at all? Couldn't you just read the contents of the file directly into bytes?
If you want bytes, use a Stream!
Why on earth are you messing with a TextReader?
EDIT:
As per your example, you are opening a file, so just use a FileStream.
The problem is with your approach to start with:
...
That's a bit like looking at an oil painting and saying, "I want the bytes for that picture, with no encoding." It doesn't make sense. Text isn't the same as binary data. Once you understand that, it's easy to get to the root of the problem. What you really want is the contents of a file as a byte array. That's easy, because files are binary data! You shouldn't be reading it as text in the first place if it isn't really text. Fortunately, .NET makes this really easy:
//convert a string to a byte array
//convert a byte array to a string
Then use this:
It returns the bytes as stored internally by .NET strings.
But all this is codswallop: A string is always linked to a particular encoding and there's no way around it. The above will fail e.g. if the file contains invalid Unicode code sequences (which may happen) or through normalization. Since you obviously don't want a
string
, don't read one. Read the file as binary data instead.