Wrox Programmer Forums
.NET Framework 2.0 For discussion of the Microsoft .NET Framework 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the .NET Framework 2.0 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old April 4th, 2008, 01:12 AM
Authorized User
Join Date: Sep 2007
Posts: 92
Thanks: 0
Thanked 0 Times in 0 Posts

It depends. If you need to use threads then of course you need to use them and that's that. If there is some lengthy work and you don't want your GUI to get stuck threads could be the answer.

But if there is a way to do your thing without using threads I suggest you do it the other way. Threads means thread context switches, which luckily aren't as slow as process context switches, but still bring some overhead. Threads can also mean synchronization problems, deadlocks, race-conditions etc.

(goes to offended mode) I know how to use threads. I've been doing programming some fifteen years. But still I would avoid them if possible.

And back to the topic... What's with the threads? :)

Similar Threads
Thread Thread Starter Forum Replies Last Post
Which Thread to use and How peace2007 ASP.NET 1.0 and 1.1 Professional 0 September 23rd, 2007 03:24 AM
abort Asynchron? ramo9941 C# 1 May 3rd, 2007 07:07 AM
Abort thread when regular expression get stuck? gurupak C# 2005 0 March 20th, 2007 02:13 AM
Problem in Thread Atif Khan C# 0 April 8th, 2005 06:57 AM
terminate a thread problem lmadhavi Visual C++ 0 November 23rd, 2004 06:20 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.