Why can't we have smart Threading? RRS feed

  • General discussion

  • I'm a huge fan of Threading .

    You gave us Threading class, Backgroundworker and now the Task class. The threading class wasn't that fun to work with, the Backgroundworker class was a bit too basic . The Tasks class still looks easy but allows more complex things and is a fun class to play with. So i'm happy with this new class but I was soooo dissapointed to see it still doesn't handle CROSS threading automaticly. Making those multiple delegates to handle my UI correctly is still a pain in the ____ and far from fun.

    Why can't we have smart threads, each .net release i'm telling my boss  "hey developing is getting so easy, in 2 years you'll make your own apps"

    Thanks for reading,



    Sunday, May 9, 2010 1:53 PM

All replies

  • Interesting feedback. Unfortunately it is miles away from my expertise. I'll try to ask our experts on this topic if there is either a good reason for the current state or if it is something .NET Framework team considers to implement in the future.

    BTW: Could you please create a small example of pseudo-code (ideally ~20 lines of code) which shows the pattern that is difficult to implement today in .NET and that you would like to see improved? (That would help me personally to understand what exactly is going on here ...)


    Sunday, May 9, 2010 9:55 PM
  • You might want to check out this blog post: http://reedcopsey.com/2009/11/17/synchronizing-net-4-tasks-with-the-ui-thread/

    Also, the Parallel Computing forums (http://social.msdn.microsoft.com/Forums/en-US/parallelextensions/threads) are a great place to get suggestions like the heard by the folks who maintain the Task APIs.


    Monday, May 10, 2010 6:04 PM