Hi,
Did you try using a parameterless catch clause? If I
remember correctly,
It should work for unmanaged exceptions as well.
---
try
{
// Use unmanaged methods from that evil component
}
catch (Exception ex)
{
// A managed exception has been thrown, perform cleanup
}
catch
{
// An unmanaged exception has been thrown, perform
cleanup
}
---
HTH,
Efran Cobisi, cobisi.com
Kirk Marple wrote:
> occasionally when running our application, a low-level
exception will take
> down our .NET service process.
>
> in the event log, i can see the fault in a system DLL
(a video codec), but
> even though we're catching exceptions at the C# level,
we don't seem to be
> able to catch these types of exceptions.
>
> is there something we have to do from a configuration
standpoint, or a
> global exception handler, that will allow us to catch
these exceptions, log
> them, clean up, and continue along safely w/o bringing
down the process?
>
> thanks,
> Kirk
>
> -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
> Kirk Marple
> Chief Software Architect, VP of Engineering
> Agnostic Media, Inc.
> e: kirk agnostic-media.com
> w: www.agnostic-media.com <http://www.agnosti
c-media.com/>
>
>
> ===================================
> This list is hosted by DevelopMentorŪ http://www.develop.com
>
> View archives and manage your subscription(s) at http://discuss.develop.com
>
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
|