Pros and Cons of using Threads in C#

Question

1.00/5 (1 vote)

See more:

Hi every one
I have understood the benefits of using threads and multithreading programming but I want to know, can we write a program without thread?

Posted 20-Aug-13 17:31pm

Behno0o0oD

Add a Solution

Comments

Sergey Alexandrovich Kryukov 21-Aug-13 0:17am

Not a correct question: it depends on what you are writing. And why? Do you think having no threads would make you life easier?

It also depends on what do you mean "without threads". You could say "single-threaded". There cannot be zero threads. :-)

—SA

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-08-20T18:33:00

Please see my comments to the question and Solution 2.

Now, the question about "pros and cons" is itself incorrect. First, you always have at least one threads. Adding more threads in many cases is not your choice, it is indirectly defined by the requirements.

For example, imagine that you got some requirements for numerical simulation: you need to calculate trajectories of some moving bodies (more exactly, worlds lines ). If the problem is solvable at all, you always can do it one thread, and it's likely the best option. Now, imagine you need to output some intermediate locations of bodies as motion progresses and give the user the power to stop motion or change some parameters on the fly. Then you will certatainly need at least one more thread. And apparently you would need at least two threads if you have to visualize the motion: one for the UI, second one for the scenario of the motion.

Are you getting the idea? It depends on scenario and requirements. Requirements should not directly dictate you to use threads, but it can be either unavoidable or highly practical (or, rather, having one thread would be extremely impractical).

And some phenomena of real life to be modeled by your application can be multithreaded by their nature. Imaging you are modeling behavior of two or more animals, each one with its own goals and behavioral program. Such independence in behavior will likely logically require a separate thread per player (animal, in this case).

No, this is not about "pros and cons". This is about what and how. :-)

—SA

Ron Beyer · Answer 2 · 2013-08-20T17:51:00

Technically no, everything runs on threads. The .NET framework takes care of threading, even just consuming events or using delegates ~~creates~~ uses threads. (Edit: To expand on that properly, delegates and events are typesafe function pointers in C# that operate on other threads. Events are a special type of delegate, and are sometimes invoked on threads other than the thread the owner of the control or object was created on.)

Can you program without explicitly creating threads (without using the Thread class, or BackgroundWorker, or ThreadPool)? Yeah, sure, but there are still threads running behind the scenes. (Edit: Threads meaning applications and other work associated with the processor, of which the task scheduler is based on threads. Your application runs on one (or more) of these threads that the processor is cycling through, so you have at least one thread in your program at all times.)

Pros and Cons of using Threads in C#

2 solutions

Solution 2

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us