>How much does it cost you and/or client to fix these issues? How much time do you waste when you have to stop what you're doing, change to the WinZip project, post a message, debug, analyze, fix, deploy, then try to get your attention back to what you were doing? Don't kid yourself that going with another tool would take longer or cost less. WinZip is nickel and diming you and/or client.

Again - Agreed. Seriously - there are dozens of ZIP libraries for .NET you can use, and once you have the basic zip/unzip/directory and add to zip functionality, everything else can be done outside the library in .NET code, and it's all managed code.
>
>>It does the job. It processes thousands of processes per day for zipping and unzipping. But, on once or twice a day, the zip functionality has a little issue. I am trying to find the reason for it. Going with another tool at this point will take longer and we have to use this one because of some very high end options that the command line is offering.