<AndrewMc...@discussions.microsoft.com> wrote:
> I don't know of any way to do this. I had the same desire to get rid of them
> so I could only view relevent information. I did find some nice information
> on how to make the output usefull. Try giving your threads names as this
> makes the thread exiting output very usefull information. For example:
>
> System.Threading.Thread MyThread = new Thread(new
> ThreadStart(MyThreadFunction));
> MyThread.Name = "MyThread";
> MyThread.Start();
>
> When you close MyThread, the output window will have the name there instead
> of a thread address or saying <No Name>. Before you close the threads or app
> though, pause the app and open the threads window from the Debug->Windows
> menu. It will bring up all active threads and the names you assigned them.
> Resume the thread and the thread names will appear in the output now instead
> of addresses etc.
>
>
>
> "john.spr...@apisoftwareinc.com" wrote:
> > Any ideas anywhere? I'm debugging .NET CF apps using the thread pool &
> > eventually the output locks up the IDE.
>
> >http://groups.google.com/group/microsoft.public.vsnet.ide/browse_thre...
>
> > On Dec 15 2002, 10:56 am, "mbro" <m_b...@videotron.ca> wrote:
> > > Is there a simple way to stop the "Threadhasexitedwithcode0" message in
> > > the debug output window of the IDE?
>
> > > I have an application with a lot of threads closing all the time and these
> > > messages make the output window unusable. There must be a very simple way,
> > > I am new in this environment.
>
> > > Thank you for your help.- Hide quoted text -
>
> - Show quoted text -