memorystream

For a .Net MemoryStream object instance, do I need to close it explicitly after using it? Or no need to close it? Which is the best practices? I am using VSTS2008 + .Net 3.5 + C#. you should close it when you are done with it. The best practice is to close the stream in the finally section of a try-catch-finally block. you can get more information here: http://msdn.microsoft.com/en-us/library/system.io.memorystream.aspx Better yet would be to use Using using (MemoryStream ms = /*get it using your favorite ctor*/) { // use it here // and now flush and copy to a file stream (for example) ws

I have a memorystream in a silverlight app. I have to copy this memorystream to a filestream object. If I call: memoryStream.Position = 0; memoryStream.Seek(0,SeekOrigin.Begin); It does not work, I debug the application, check the properties of the memorystream, and the position still points to the end of the file. Any clues? Is it possible that another of your properties is being triggered in the debugger, and reading through the stream? Rather than using the debugger, what happens if you log (or show on a message box): Log("Position = " + stream.Position); stream.Position = 0; Log("Position

I am trying to send a .jpg file which is on my android device to my server computer. To do this, I am converting the picture into a byte array by a java android application, and sending it as an argument to my server computer. I`m doing this by a web service call. The first function is edited: public static byte[] ImageConvertion(){ File inputFile = new File("/storage/emulated/0/IFSpictures/icon-si_strapclamp.jpg"); byte[] data; try{ FileInputStream input = new FileInputStream(inputFile); ByteArrayOutputStream output = new ByteArrayOutputStream (); byte[] buffer = new byte[65535]; int l; while

I'm serializing an object to a byte[] using MemoryStream : byte[] serialized = new byte[1000]; using (MemoryStream stream = new MemoryStream(serialized)) using (TextWriter textWriter = new StreamWriter(stream)) serializer.Serialize(textWriter, stuffToSerialize); is there any way I can set 'serialized' to grow according to the size of the stuffToSerialize ? The parameterless constructor new MemoryStream() uses one. Then serialise into it, and then when you need the byte[] call ToArray() which creates a copy of whatever length of the buffer was actually used (the internal buffer will generally

I have a MemoryStream which is created from a File at runtime. Then the MemoryStream is edited and some bytes are removed. Now I have to maintain a Constant Filesize so I have to fill the MemoryStream with 0xFF bytes.. What is the Fastest way to Do this Operation? I know, that I always can loop through the MemoryStream sizes and add 0xFF's but I need to know a faster and more efficient way to do it! If you have many bytes to write to the stream, it may be more efficient to write a array rather than each byte individually: static void Fill(this Stream stream, byte value, int count) { var buffer

How can i create a file and write to it using the memory stream? I need to use the memorystream to prevent other threads from trying to access the file. The data i'm trying to save to a file is html. How can this be done? (Presuming you mean how to copy a file's content to a memory stream) If you are using framework 4: MemoryStream memoryStream = new MemoryStream(); using (FileStream fileStream = new FileStream(FilePath, FileMode.Open, FileAccess.Read)) { fileStream.CopyTo(memoryStream); } Jayesh Sorathia Here are code to create file byte[] data = System.Text.Encoding.ASCII.GetBytes("This is a