If you’re going to start a long-running task with TPL, you should specify TaskCreationOptions.LongRunning, which will mean it doesn’t schedule it on the thread-pool. (EDIT: As noted in comments, this is a scheduler-specific decision, and isn’t a hard and fast guarantee, but I’d hope that any sensible production scheduler would avoid scheduling long-running tasks on a thread pool.)
You definitely shouldn’t schedule a large number of long-running tasks on the thread pool yourself. I believe that these days the default size of the thread pool is pretty large (because it’s often abused in this way) but fundamentally it shouldn’t be used like this.
The point of the thread pool is to avoid short tasks taking a large hit from creating a new thread, compared with the time they’re actually running. If the task will be running for a long time, the impact of creating a new thread will be relatively small anyway – and you don’t want to end up potentially running out of thread pool threads. (It’s less likely now, but I did experience it on earlier versions of .NET.)
Personally if I had the option, I’d definitely use TPL on the grounds that the Task API is pretty nice – but do remember to tell TPL that you expect the task to run for a long time.
EDIT: As noted in comments, see also the PFX team’s blog post on choosing between the TPL and the thread pool:
In conclusion, I’ll reiterate what the CLR team’s ThreadPool developer has already stated:
Task is now the preferred way to queue work to the thread pool.
EDIT: Also from comments, don’t forget that TPL allows you to use custom schedulers, if you really want to…