{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "",
    "ClosedDate": null,
    "CommentCount": 0,
    "Custom": null,
    "Description": "It would be nice if the ZipFile.ExtractAll() method could extract to a Stream rather than allowing only a path. This would allow, for example, extracting to a MemoryStream in cases where saving to the disk isn't actually necessary.",
    "LastUpdatedDate": "2013-02-21T18:43:16.74-08:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2011-03-23T06:04:08.687-07:00",
    "Status": {
      "Name": "Proposed",
      "Id": 1
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "Allow ZipFile.ExtractAll() to extract to a Stream",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 13225
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "Interesting senfo; what does it mean to \"extract all\" into a stream?  All of the content is just concatenated all together?  I suppose you could do this pretty easily with your own loop, just calling Extract() and passing the same stream each time.  So there's an easy workaround. \r\n\r\nI'd like to understand the scenario though.  When would you ever want to extract everything into a single stream? \r\n",
      "PostedDate": "2011-06-18T09:22:36.7-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:43:16.74-08:00",
      "Id": -2147483648
    }
  ]
}