43 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Radudu commented  ·  November 15, 2010 5:45 a.m.  ·  Delete

  I squeezed my head until I read it's not yet implemented.....

  I want it.

• Angel commented  ·  October 18, 2010 6:29 p.m.  ·  Delete

  It's required!!!

• Peter commented  ·  October 14, 2010 7:08 a.m.  ·  Delete

  would be very helpful for handling the Async WCF calls in silverlight.

• Rajesh commented  ·  October 12, 2010 3:53 a.m.  ·  Delete

  need it as it will increases the performance silverlight application .

• James Hardaker commented  ·  October 12, 2010 3:50 a.m.  ·  Delete

  This would be very useful. Votes++.

• aLEKSANDR commented  ·  September 30, 2010 6:47 a.m.  ·  Delete

  i NEED IT!!

• Paul Wade commented  ·  September 24, 2010 5:15 p.m.  ·  Delete

  Make it so! :)

• Chris Moore commented  ·  September 23, 2010 4:59 a.m.  ·  Delete

  Can we please simply have a "client profile" that is applicable to both Silverlight and WPF apps? And assembly-level compatibility for framework components that define this profile? And no, don't dumb-down the profile but, rather, augument Silverlight to include those aspects it doesn't currently have. If those criteria were satisfied, a significant number of suggested features on this list would evaporate.

• Chris Moore commented  ·  September 23, 2010 4:59 a.m.  ·  Delete

  Can we please simply have a "client profile" that is applicable to both Silverlight and WPF apps? And assembly-level compatibility for framework components that define this profile? And no, don't dumb-down the profile but, rather, augument Silverlight to include those aspects it doesn't currently have. If those criteria were satisfied, a significant number of suggested features on this list would evaporate.

• prabhakar commented  ·  September 15, 2010 12:27 a.m.  ·  Delete

  PLINQ is a gr8 feature. It would be gr8 if it is added to SL 4.

• dotnet4life commented  ·  September 7, 2010 2:06 p.m.  ·  Delete

  Please add support for TPL & concurrent collections in the next version of Silverlight. It would make app code cleaner & easier to read and maintain.

• Adron Hall commented  ·  August 30, 2010 7:52 a.m.  ·  Delete

  Very kewl idea... I dig it. Not a really big fan of the threading options in Silverlight right now to begin with. So it would be nice to have more...

  ...and that could lead to a host of other things.

• Rockford Lhotka commented  ·  August 30, 2010 7:48 a.m.  ·  Delete

  Thanks for that link. I have a codebase that spans .NET and SL. Right now I have a bunch of #if statements to use the elegant .NET features on .NET, and clunky hand-crafted implementations on SL. That makes me sad, as I'm basically maintaining two implementations for everything thread-related. This is why I want SL to catch up to .NET in this important area.

• herzmeister der welten commented  ·  August 30, 2010 2:48 a.m.  ·  Delete

  Lazy<T> is available but will block if used on the UI thread. Thus it is usable only in dedicated model threads which are employed in advanced scenarios like the one described here: http://www.codeproject.com/KB/silverlight/Mtvt.aspx

• Boris commented  ·  August 15, 2010 4:13 p.m.  ·  Delete

  +1 This would be really cool.

• Ming Man commented  ·  July 30, 2010 7:23 p.m.  ·  Delete

  We want System.Threading.Task to be in Silverlight. It is reasonable for Silverlight to be able to do parallel programming easier.

• Ayubu commented  ·  July 27, 2010 10:00 a.m.  ·  Delete

  Very important

• Suresh Thennarangam commented  ·  July 20, 2010 7:32 p.m.  ·  Delete

  This would raise Silverlight to the level of a serious business grade software development platform.

• Jose Luis Latorre commented  ·  April 30, 2010 2:03 a.m.  ·  Delete

  Silverlight was born as a multi-thread plug-in that takes advantage of its native multi-cpu/core support... so let it have it... it's its natural evolution. Doing else would be crazy and like putting a finger between a bycicle wheel (when it is on the run). it would hurt a lot and also stop the cycle (or not).

• Bruce Leggett commented  ·  April 23, 2010 12:47 p.m.  ·  Delete

  I agree. Silverlight should have EVERYTHING WPF has!