{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "Won't fix.",
    "ClosedDate": "2011-06-13T10:57:07.127-07:00",
    "CommentCount": 0,
    "Custom": null,
    "Description": "Hi,\n \nI just spent an hour trying to figure out why I had no data when extracting to stream. Would it be possible to reset the stream position to zero when the the Extract method completes? It would save people some headache trying to find the error. Below is the routine I use to extract data.\n \n            var ms = new MemoryStream();\n            entry.Extract(ms);\n            ms.Position = 0;\n            var reader = new StreamReader(ms);\n \nThe ms.position = 0 should not be needed in my humble opinion.",
    "LastUpdatedDate": "2013-05-16T05:31:46.15-07:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2010-07-12T07:59:38.887-07:00",
    "Status": {
      "Name": "Closed",
      "Id": 4
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "Extract to Stream does not reset the streams position to zero",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 11494
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "Terribly sorry you had this problem.  Unfortunately it is not correct behavior to always Seek() before extracting to a stream.  There are some streams that do not handle Seek(), and so it would make no sense.  There is a way to test for this (CanSeek()), but even in the case where a stream is seekable, in the general case the extraction should not seek to the beginning.  \r\n\r\nSo I'm going to reject this as Not-a-Bug. \r\n",
      "PostedDate": "2011-06-13T10:56:56.3-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2011-06-13T10:57:07.127-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:43:28.97-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-05-16T05:31:46.15-07:00",
      "Id": -2147483648
    }
  ]
}