类库（可用于Universal Apps移植）System.Threading.Thread的限制

Question

I use Visual Studio 2013 Ultimate Update 4 to create a new project of type "Class Library (Portable for Universal Apps)". The resulting PCL is targeted at two platforms ie Windows 8.1 and Windows Phone 8.1 and this is what I need.

System.Threading.Thread class is not supported in this subset. When I widen the assembly targeting with two more platforms (.NET Framework 4.5.1 and Silverlight 5) the System.Threading.Thread mystically shows up and becomes available. I tried to use it and it works perfectly being run by both Windows.Phone 8.1 and Windows 8.1 Store apps.

Did I get it right that the System.Threading.Thread class is simply hidden from the "default" PCL configuration in order to push developers towards async/await pattern?

Leaving behind the comparison of advantages and draws of different asynchronous execution and thread management models, are there any technical drawbacks in utilizing the System.Threading.Thread class in the mentioned scenario?

Thanks in advance.

Answer 1

After some discussion with David Kean from the .NET team, this is expected behaviour but note that you do not get access to the full .NET Thread class; you only get a couple of things like ManagedThreadId and CurrentUICulture .

So you still need to use either the thread pool or the task-based APIs in order to run parallel operations.