CiaranODonnell
Tue Jul 22 10:24:01 CDT 2008
Try attaching a debugger to it with the solution loaded and pausing the
application, on the 'Debug Location' toolbar, look at each of the threads in
turn and see if the code they are executing gives you any clues. It might be
on a blocking call to something.
--
Ciaran O''Donnell
http://wannabedeveloper.spaces.live.com
"John" wrote:
> Its just a winform app that runs a series of queries on an access backend
> database. Can't think of anything special.
>
> Thanks
>
> Regards
>
> "Patrice" <
http://www.chez.com/scribe/> wrote in message
> news:uEYvxh96IHA.1200@TK2MSFTNGP04.phx.gbl...
> > It's likely that your application is kept alive. Instead of forcing the
> > application to quit my personal preference would be likely to find out
> > what keeps the app aliave and to perform the appropriate cleanup... See
> > what could keep a reference to your app such as perhaps a callback to
> > would be kept by the system...
> >
> > --
> > Patrice
> >
> > "John" <info@nospam.infovis.co.uk> a écrit dans le message de groupe de
> > discussion : #yGrb266IHA.392@TK2MSFTNGP03.phx.gbl...
> >> Hi
> >>
> >> I have a winform app. When this app is closed it remains under
> >> 'Processes' in Task Manager. What is the problem and how can I ensure
> >> that app closes completely and releases all resources?
> >>
> >> Thanks
> >>
> >> Regards
> >>
> >
>
>
>