Brian,

Yeah, duh, I wasn't thinking. What I should have suggested was to put *everything* in the try, like this:

try
{
  XceedZipLib.XceedZipClass loZipper = new XceedZipLib.ZceedZipClass();
  loZipper.PreservePaths = false;
  loZipper.FilesToProcess = etc....

}
catch
{
   MessageBox.Show("etc.");
}

~~Bonnie


>Brian,
>>
>>How about this:
>>

>>object loZipper;
>>try
>>{
>>   // etc.
>>}
>>//  etc.
>>

>>
>>~~Bonnie
>
>
>
>Hi Bonnie,
>
>That too will cause the compile error:
>
>A local variable named 'loZipper' cannot be declared in this scope because it would give a different meaning to 'loZipper', which is already used in a 'parent or current' scope to denote something else
>
>Plus, I lose the intellisense since the loZipper declaration in scope outside of the try-catch is simply object. I think I'm just going to drop the try-catch all together.
>
>I would think trapping for this kind of thing would be a common need, no?
>
>
>- Brian