You can call Application.Exit, which is a fairly gentle shutdown, or call Environment.Exit, which is equivalent to killing the process (very abrupt end).
Neither are what I would prefer to do, as in the past there have always been some resources that didn't get cleaned up. In the .NET world, they'll probably get freed ... eventually.
I would try and find a way to gracefully unwind your call stack, cleaning up as you go.
Chip H.
____________________________________________________________________ If you want to get the best response to a question, please read FAQ222-2244 first
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.