A stream is a way of sequentially accessing a file. A byte stream access the file byte by byte. A byte stream is suitable for any kind of file, however not quite appropriate for text files. For example, if the file is using a unicode encoding and a character is represented with two bytes, the … Read more
fgetc+ungetc. Maybe something like this: int fpeek(FILE *stream) { int c; c = fgetc(stream); ungetc(c, stream); return c; }
FileAccess says what you are going to do with the file. Pretty easy to understand, you’ll know you are going to read or write. FileShare is the much trickier one since it requires you to step into the shoes of another programmer. It determines what another process can do if it also has the file … Read more
They are not byte-order marks but a length-prefix, according to MSDN: public virtual void Write(string value); Writes a length-prefixed string to [the] stream And you will need that length-prefix if you ever want to read the string back from that point. See BinaryReader.ReadString(). Additional Since it seems you actually want a File-Header checker Is it … Read more
The code you show, reads all content of the 500mb file into a contiguous region in memory. It’s not surprising that you get an out-of-memory condition. The solution is, “don’t do that.” What are you really trying to do? If you want to read a file completely, it’s much simpler than the ReadFully method you … Read more
An easy one as an extension method public static class Extensions { public static Stream ConvertToBase64(this Stream stream) { byte[] bytes; using (var memoryStream = new MemoryStream()) { stream.CopyTo(memoryStream); bytes = memoryStream.ToArray(); } string base64 = Convert.ToBase64String(bytes); return new MemoryStream(Encoding.UTF8.GetBytes(base64)); } }
Stefan S. said: I understand that .NET FileStream’s Flush method only writes the current buffer to disk No, .NET FileStream’s Flush only writes the .NET buffers to the OS cache, it does not flush the OS cache to disk. Sadly the MSDN doc on this class doesn’t say that. For .NET < 4.0, you’ll have … Read more
Default buffer size is 4 KiB. Also, take a look here: Sequential File Programming Patterns and Performance with .NET Programming patterns for sequential file access in the .NET Framework are described and the performance is measured. The default behavior provides excellent performance on a single disk – 50 MBps both reading and writing. Using large … Read more
Ok, two edits later… This should work. The first time I tried it I think I had forgotten to set FileMode.Append on the oStream. string test = “foo.txt”; var oStream = new FileStream(test, FileMode.Append, FileAccess.Write, FileShare.Read); var iStream = new FileStream(test, FileMode.Open, FileAccess.Read, FileShare.ReadWrite); var sw = new System.IO.StreamWriter(oStream); var sr = new System.IO.StreamReader(iStream); var … Read more
You need to specify the append open mode like #include <fstream> int main() { std::ofstream outfile; outfile.open(“test.txt”, std::ios_base::app); // append instead of overwrite outfile << “Data”; return 0; }