{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "Fixed in changeset 81671.  The new behavior is to catch a PathTooLongException, then create and throw a new ZipException that specifies the offending path, passing the PTLE as an inner exception.  The first binary that will have this change available will be v1.9.1.8",
    "ClosedDate": "2011-08-06T15:12:29.69-07:00",
    "CommentCount": 0,
    "Custom": null,
    "Description": "from http://dotnetzip.codeplex.com/discussions/267600 \n \nI encountered the System.IO.PathTooLongException, using ZipFile.AddDirectory() to save a zip. Problem here, the resulting exception doesn't even say which path was too long . Using the DotNetZip devkit I saw this happened in ZipEntry.Create when File (Directory) will be first accessed with File.GetLastWriteTime(filename) (ZipEntry.cs line 2402). \n \nThe path really was too long. A subdirectory of the directory I wanted to zip had a path longer than 259 characters (267 :) ), apparently the maximum path length the .NET IO system can handle. So the error was due to the .net limit. I found a nice blog post about this and how to use Win32 to access file/folders with >260 path length.  http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-paths-in-net-part-1-of-3-kim-hamilton.aspx\n \nIf you zip such a directory, the whole process fails. What really bothered me was to find out which file/directory was too long, because the PathTooLongException doesn't return the path value. So it would be nice if you would catch this PathTooLongException and return a custom exception that tells u the path.",
    "LastUpdatedDate": "2013-06-20T07:05:42.723-07:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2011-08-06T11:19:59.14-07:00",
    "Status": {
      "Name": "Closed",
      "Id": 4
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "DotNetZip should be kinder when throwing PathTooLongException",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 14035
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "I tried this, but I still can't get the long path. Can you explain better? Tks.",
      "PostedDate": "2012-02-27T11:04:27.75-08:00",
      "Id": -2147483648
    },
    {
      "Message": "I am curious at to why the \"too long\" file name was not simply included in the message of the Path Too Long Exception (PTLE)?\r\n\r\nE.g.\r\n\r\nThe specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters: \r\n[C:\\dfljls\\sdf\\sdf\\d\\fs\\dfsfsfsdfad\\jfsdkljfljadjk.jfkd]",
      "PostedDate": "2012-08-09T06:36:03.407-07:00",
      "Id": -2147483648
    },
    {
      "Message": "This is a Windows* OS/file system issue.The cause is directory paths on the drive is longer than 255 characters (including spaces).There's a lot of  additional softwares which can fix this problem like Long Path Tool.\nhttp://PathTooDeep.com \nLong Path Tool can simplify and probably end your problems in unlocking, managing and renaming files that appear to have a long filename.",
      "PostedDate": "2012-11-19T06:56:07.4-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:43:06.643-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-05-16T05:31:31.84-07:00",
      "Id": -2147483648
    },
    {
      "Message": "Long path tool is the best solution for your problem. try it and solve your problem.",
      "PostedDate": "2013-06-20T07:05:42.723-07:00",
      "Id": -2147483648
    }
  ]
}