I recently found myself needing a typesafe \"fire-and-forget\" mechanism for running code asynchronously.
Ideally, what I would want to do is somet
The compiler-generated BeginInvoke
method is also called on the thread pool (reference). So I think ThreadPool.QueueUserWorkItem would be alright, except that you're being a bit more explicit about it I guess (and I suppose a future CLR could choose to run BeginInvoke
'ed methods on a different thread pool).