Is there a nice simple method of delaying a function call whilst letting the thread continue executing?
e.g.
public void foo()
{
// Do stuff!
// Delayed call to bar() after x number of ms
// Do more Stuff
}
public void bar()
{
// Only execute once foo has finished
}
I'm aware that this can be achieved by using a timer and event handlers, but I was wondering if there is a standard c# way to achieve this?
If anyone is curious, the reason that this is required is that foo() and bar() are in different (singleton) classes which my need to call each other in exceptional circumstances. The problem being that this is done at initialisation so foo needs to call bar which needs an instance of the foo class which is being created... hence the delayed call to bar() to ensure that foo is fully instanciated.. Reading this back almost smacks of bad design !
EDIT
I'll take the points about bad design under advisement! I've long thought that I might be able to improve the system, however, this nasty situation only occurs when an exception is thrown, at all other times the two singletons co-exist very nicely. I think that I'm not going to messaround with nasty async-patters, rather I'm going to refactor the initialisation of one of the classes.
It's indeed a very bad design, let alone singleton by itself is bad design.
However, if you really do need to delay execution, here's what you may do:
This will, however, invoke
bar()
on a separate thread. If you need to callbar()
in the original thread you might need to movebar()
invocation toRunWorkerCompleted
handler or do a bit of hacking withSynchronizationContext
.Building upon the answer from David O'Donoghue here is an optimized version of the Delayed Delegate:
The class could be slightly more improved by using a unique key for the delegates. Because if you add the same delegate a second time before the first one fired, you might get a problem with the dictionary.
Thanks to modern C# 5/6 :)
It sounds like the control of the creation of both these objects and their interdependence needs to controlled externally, rather than between the classes themselves.
Well, I'd have to agree with the "design" point... but you can probably use a Monitor to let one know when the other is past the critical section...
This will work either on older versions of .NET
Cons: will execute in its own thread
Usage: