Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 years ago.
Improve this question
Is there any functionality in C# with Web, so that from UI, if a button is pressed, the execution should get stopped. (Here C# is already busy with some process execution)
For example:
while (something)
{
// do something
}
while (something)
{
// do something
}
If first while loop is under execution and from UI "stop execution" button is pressed then it should interrupt the whole execution and exit.
You mean like this?
private volatile bool _stop = false;
void OnCancelClick()
{
_stop = true;
}
void WorkerProcess() //In separate thread
{
while (!_stop)
{
// do something
}
}
There are a million ways to do it. This is probably the simplest to understand.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Consider a server with a performance-sensitive, highly-parallel, C# processing pipeline where we want to raise an event if something stops happening, e.g. the flow of media.
One theorized approach is to create a timer that is delayed continuously by the pipeline. By way of a simplistic example:
const int IDLE_MILLIS = 1000; // 1 second
Timer timer = new Timer(IDLE_MILLIS, () =>
{
Console.WriteLine("Pipeline is idle.");
});
void ProcessMediaFrame(MediaFrame frame)
{
timer.Change(IDLE_MILLIS, Timeout.Infinite);
// pipeline is not idle
}
How expensive is the Change method here? (https://learn.microsoft.com/en-us/dotnet/api/system.threading.timer.change)
Does the Timer consume any resources while idle?
The performance note in the source code (thanks Codexer for linking the correct file) says your case is exactly what they've optimized for.
We assume that timers are created and destroyed frequently, but rarely actually fire.
...
timeouts for operations ... almost never fire, because the whole point is that the timer only fires if something has gone wrong.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
If I have following
public async Task<Owner> Get(int carId)
{
var car = await myDbContext.Cars.FindAsync(carId);
return car.Owner;
}
I cannot access the Owner property in the first line cause it's a async call.
If I access it using await myDbContext.Cars.FindAsync(carId).Result.Owner does that mean that I'll get stuck in a deadlock sometime or does it have some other side effects?
The difference between your current code and using .Result is that, currently, the caller of the Get(...) method will be able to continue, until awaiting themselves.
Using .Result in the Get(...) method will block any caller at that point, until the result is available, and is therefore discouraged.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
Because task can not run twice (it would throw an exception). I am creating ahead 2 tasks.
Is there a nice way to duplicate a task instead, something maybe like that:
Task t1 = new Task();
Task t2 = new Task(t1);
Do you truly need to clone a task? If not then one way to achieve the same outcome would be to first create an Action and then create two tasks that take the same Action.
var work = new Action(() =>
{
// do work here
});
var t1 = new Task(work);
var t2 = new Task(work);
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I have a background worker that executes evry time when data recived on serial port, and inside is some code, i would like to play some music file, just the first time that background worker executes, can somebody please help me ?
code:
private void backgroundWorker1_DoWork(object sender, DoWorkEventArgs e)
{
.....
s.play();
...
}
I would probably just use a boolean class level field and set it after first call to DoWork, and then check in each call to see if you need to initiate play.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
What is the Mutex and semaphore in C#? Where we need to implement?
How can we work with them in multithreading?
You should start at MSDN.
System.Threading.Mutex: A synchronization primitive that can also be used for interprocess synchronization.
System.Threading.Semaphore: Limits the number of threads that can access a resource or pool of resources concurrently.
Generally you only use a Mutex across processes, e.g. if you have a resource that multiple applications must share, or if you want to build a single-instanced app (i.e. only allow 1 copy to be running at one time).
A semaphore allows you to limit access to a specific number of simultaneous threads, so that you could have, for example, a maximum of two threads executing a specific code path at a time.
I'd start by reading this: http://www.albahari.com/threading/part2.aspx#_Synchronization_Essentials
and then bolster it with the MSDN links bobbymcr posted.
You might want to check out the lock statement. It can handle the vast majority of thread synchonization tasks in C#
class Test {
private static object Lock = new object();
public function Synchronized()
{
lock(Lock)
{
// Only one thread at a time is able to enter this section
}
}
}
The lock statement is implemented by calling Monitor.Enter and Monitor.Exit. It is equivalent to the following code:
Monitor.Enter(Lock);
try
{
// Only one thread at a time is able to enter this section
}
finally
{
Monitor.Exit(Lock);
}