If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Refactoring from Threads to Tasks

Hi,

I plan to build a refactoring tool that converts Thread usages to corresponding Task constructs. This transformation will open the gate to new features (async/await, Parallel class, PLINQ) for the application. After this transformation, the refactoring tool searches Task usages which are able to use Parallel.For(Each), and Parallel.Invoke. This two step process will have some advantages in terms of performance, readability, scalability, functionality, etc. Do you think that this kind of refactoring tool is useful for the developers? As you know, refactoring tools are good for error-prone transformations and do you observe that developers introduce bugs when they transform Threads to Tasks? I know that the transformation is not straightforward because, for instance, Threads with I/O bound computations should be converted to LongRunning Tasks. Is there any other corner cases like this?

* The Perfect Platform for Game Developers: Android
Developing rich, high performance Android games from the ground up is a daunting task. Intel has provided Android developers with a number of tools that can be leveraged by Android game developers.

* The Best Reasons to Target Windows 8
Learn some of the best reasons why you should seriously consider bringing your Android mobile development expertise to bear on the Windows 8 platform.