[
  {
    "Id": "70619",
    "ThreadId": "21223",
    "Html": "\r\nHow can one create auto-extracting zip files?<br />",
    "PostedDate": "2008-01-29T08:55:19.92-08:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "70859",
    "ThreadId": "21223",
    "Html": "<p>This library does not currently do auto-extracting zip files. sorry.</p>\r\n<p style=\"color:Red;font-style:italic\">[Update: as of v1.8.3.15, DotNetZip can produce self-extracting archives with a run-on-extract command.]</p>",
    "PostedDate": "2008-01-30T10:20:46.553-08:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "70958",
    "ThreadId": "21223",
    "Html": "\r\nNo problem. The library works great nonetheless. <br /><br />FWIW, I found this free component, http://www.zip-compression.com/self-extracting-exe.asp#download , that seems to have a command-line API, so I might try that.<br />",
    "PostedDate": "2008-01-30T20:59:47.747-08:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "71273",
    "ThreadId": "21223",
    "Html": "\r\nAs a follow-up to my post above, note that the ChilKat componet http://www.zip-compression.com/self-extracting-exe.asp#download does work but it did not work for my purposes.<br /><br />It does not work in my \"SetupPackager\" project because I need the setup.bat file (which is included in the zip and which ultimately performs the install) to delete itself along with the extraction directory and the extraction exe and everything else except a log file that it writes and, under those conditions it seems, that the self-extracting exe created by ChilKat cannot do that. (I could be wrong-- but, I am sure that do not have any time for any more testing on it.)<br /><br />Furthermore, note that the self-extracting exe needed to prompt the user for a destination directory, which ends up being about as many clicks as if one just right-clicks in Windows Explorer and chooses \"extract all\". Therefore, we are not going to bother creating self-extracting exes.<br /><br />That said, we have the DotNetZip component integrated and it works great. It builds a 20MB zip in less-than 10 seconds. Nice work and THANK YOU.<br />",
    "PostedDate": "2008-02-01T11:52:52.19-08:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "97451",
    "ThreadId": "21223",
    "Html": "Update; as of v1.5, the library does self-extracting zip files.<br>\r\n",
    "PostedDate": "2008-06-07T16:32:23.35-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "99692",
    "ThreadId": "21223",
    "Html": "<div class=radEditorContent id=\"ctl00_ctl00_Content_TabContentPanel_Content_PostRepeater_ctl12_BodyDiv\">ps:&nbsp;don't forget, DotNetZip is now donationware.<br>\r\nI am now <a class=externalLink href=\"http://cheeso.members.winisp.net/DotNetZipDonate.aspx\"><span style=\"color:#3e62a6\">accepting donations<span class=externalLinkIcon></span></span></a> on behalf of my favorite charity. <br>\r\nIf you find IIRF useful, consider donating. </div>\r\n",
    "PostedDate": "2008-06-18T22:19:30.06-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "101989",
    "ThreadId": "21223",
    "Html": "Is there a way to have the self-extractor run a file after the self-extraction is complete-- such as &quot;launch setup.bat after extraction&quot;?\r\n",
    "PostedDate": "2008-07-01T13:54:38.453-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "102076",
    "ThreadId": "21223",
    "Html": "<p>There is no way to do that today.</p>\r\n<p>I will add that as a workitem for DotNetZip.</p>\r\n<p style=\"color:Red;font-style:italic\">[Update: as of v1.8.3.15, in May 2009, DotNetZip can produce self-extracting archives with a run-on-extract command.]</p>",
    "PostedDate": "2008-07-02T00:10:04.663-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "196607",
    "ThreadId": "21223",
    "Html": "<p>Hi,</p>\r\n<p>I'd be very interested in running a file when the extraction has finished.</p>\r\n<p><br>Also, it would be great if&nbsp;the command-line extractor's return code was the same as the one of the file that was run.<br>For example, we have a few scenarios where we bundle MsBuild scripts as self-extracting exes.<br>It would be very helpful if we could run the extractor, and check its return code to know if the scripts ran fine.</p>\r\n<p>Thanks</p>",
    "PostedDate": "2009-06-01T16:30:56.79-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "196656",
    "ThreadId": "21223",
    "Html": "This discussion has been copied to a work item. Click <a href=\"http://dotnetzip.codeplex.com/WorkItem/View.aspx?WorkItemId=7836\">here</a> to go to the work item and continue the discussion.",
    "PostedDate": "2009-06-01T20:38:53.06-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "196660",
    "ThreadId": "21223",
    "Html": "<p>In the current v1.8 of DotNetZip, there is already a run-on-extract feature for self-extracting archives.</p>\r\n<p>It does not yet include the exit-code handling you described.</p>",
    "PostedDate": "2009-06-01T20:50:43.593-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "196665",
    "ThreadId": "21223",
    "Html": "<p>Thanks for your prompt reply!<br>I will download the 1.8 preview to give it a try.</p>",
    "PostedDate": "2009-06-01T20:59:43.877-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "196695",
    "ThreadId": "21223",
    "Html": "<p>ok, v1.8.3.15, now available, has the exit-code handling for the run-on-extract command&nbsp;on the CommandLine flavor of the SFX.</p>\r\n<p>&nbsp;</p>",
    "PostedDate": "2009-06-01T22:51:34.663-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  }
]