{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "fixed in changeset 33089.  The new method is called AddEntry().  First bin release: v1.8.3.23. ",
    "ClosedDate": "2009-06-14T17:58:57.537-07:00",
    "CommentCount": 0,
    "Custom": null,
    "Description": "There are already methods called AddFileFromString and AddFileFromStream.  Please add a new AddFileFromByteArray() method.\n \nThe possibility to synthesize any arbitrary binary content (lets say, some encrypted text or a JPEG image) solely in memory and insert it directly into a ZIP file would be an excellent capability.\n \nZipEntry AddFileFromByteArray(string fileName, string directoryPathInArchive, byte[] buffer)",
    "LastUpdatedDate": "2013-05-16T05:32:19.44-07:00",
    "PlannedForRelease": "1.9.1.5 DotNetZip",
    "ReleaseVisibleToPublic": true,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2009-06-05T09:21:31.577-07:00",
    "Status": {
      "Name": "Closed",
      "Id": 4
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "add new method: AddFileFromByteArray()",
    "Type": {
      "Name": "Feature",
      "Id": 1
    },
    "VoteCount": 3,
    "Id": 7860
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "Yes! Yes! Yes! (Did I said who proposed this? Surprise! Just me! X-D",
      "PostedDate": "2009-06-08T03:58:09.937-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2009-06-09T05:24:47.413-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2009-06-13T12:27:34.047-07:00",
      "Id": -2147483648
    },
    {
      "Message": "Thinking about this a little - it would be nice to re-factor the method names for the AddFileFromXxxx family.  There is now AddFileFromString, AddFileFromStream, and we're considering AddFileFromByteArray.  Each method behaves the same way, takes the same arguments, except for the source of the data.  Does it make sense to create a method family with 3 overloads?   If not, why not?  If so, What should be the name of the method?   AddFileFromMemory?   AddFileEx ?   any suggestions? ",
      "PostedDate": "2009-06-13T12:30:39.293-07:00",
      "Id": -2147483648
    },
    {
      "Message": "If I can come up with a new name that makes sense, then I'll add a byte[] variant of the method, and mark the existing methods AddFileFromString and AddFileFromStream as obsolete in v1.8.  I'll make a decision on that in the next couple days. ",
      "PostedDate": "2009-06-13T12:35:12.293-07:00",
      "Id": -2147483648
    },
    {
      "Message": "What about AddEntry()?  Three overloads, one for String, Stream, and byte[].  ",
      "PostedDate": "2009-06-14T14:34:25.7-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2009-06-14T17:58:57.537-07:00",
      "Id": -2147483648
    },
    {
      "Message": "Sorry, I've been out for some days.\r\n\r\nThank you very much. A single, overloadeable method is a good one, which it could be expanded in the future for other kind of items.",
      "PostedDate": "2009-06-20T00:38:55.183-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:44:15.56-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-05-16T05:32:19.44-07:00",
      "Id": -2147483648
    }
  ]
}