Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Wolfgang Riedmann" Newsgroups: comp.lang.clipper.visual-objects Subject: Re: Terminating an application which runs in the background Date: Fri, 24 Mar 2017 09:17:23 +0100 Lines: 28 Message-ID: References: <0c459c45-4199-4fd7-acac-e6c5f2e66b58@googlegroups.com> <5a9a7f2c-3cf1-460a-aa98-7d1715b056bd@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: individual.net hObtjod4JfqUU/BtSzDILAKDXwqv/PAZpaG1JbMFxpxp7onPg= Cancel-Lock: sha1:AIqrnm8lTLoMSsEmTQHt+NPyUe0= User-Agent: XanaNews/1.18.1.6 Xref: csiph.com comp.lang.clipper.visual-objects:10340 Hi Karl, > > P.S. unfortunately such a powerful feature is missing in the .NET > > framework > > I'm just taking my first steps in .NET. Somewhere I found somemthing > similar to VO-Error-handling. Used this in my first app and it works > pretty well. But please don't ask for explanations... in VO you have a global unique errorhandler. In .NET, you have to call it from several different places in try/catch sequences. In VO, even if you have not a single begin/end sequence, your installed error handler is called. In .NET unfortunately it is not that easy.... In my experience if you have not the try/catch sequence in the right place, you'll receive the errors in the wrong places. I have to confess that I have to find the best solution for my applications yet - but there is so many new in .NET and WPF to learn, that I have enough to do for the next 5 years at least.... Wolfgang --