[
  {
    "Id": "1012041",
    "ThreadId": "435818",
    "Html": "Hi, I've been working on a small app that uses DotNetZip to handle packaged files.  It works perfectly, but when I turned on all the exception debugging (as sort of a last pass before the app goes in for testing), I found that any use of wildcards returns a first-chance exception claiming that there are invalid characters in the path.  For instance, this line:\r<br />\n<br />\n  ICollection&lt;ZipEntry&gt; myFiles = myZip.SelectEntries(&quot;(name != *.bla)&quot;);\r<br />\n<br />\nthrows the exception, whereas if I just simply remove the *, then no exception fires (although the results are not what I want - I need that wildcard):\r<br />\n<br />\n  ICollection&lt;ZipEntry&gt; myFiles = myZip.SelectEntries(&quot;(name != .bla)&quot;);\r<br />\n<br />\nIt's clearly not a problem with anything else, such as the path to the zip itself, since that second line fires no exception whatsoever.\r<br />\n<br />\nI know it may be a moot point (since the app appears to be working perfectly fine despite the exceptions), but I'm not a fan of seeing exceptions like this firing.  I've tried it with brackets, without brackets, with single quotes, without single quotes, and several other methods, and all results are the same - if the * is present, the call fires an exception (although the return value is exactly what I wanted).\r<br />\n<br />\nAm I doing something wrong here?<br />\n",
    "PostedDate": "2013-03-07T13:57:09.147-08:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  }
]