Showing archive results for 2009

The Task Parallel Library is centered around the Task class and its derived Task<TResult>. The main purpose of these types is to represent the execution of an asynchronous workload and to provide an object with a means to operate on that workload, whether it be to wait for it, to continue from it, or the like. The primary type of asynchronous...

Today we are announcing the availability of FREE HOSTING accounts for web developers to try out the new feature sets of Visual Studio 2010 Beta1, ASP.NET 4 Beta1 and Microsoft Web Deployment Tool (MsDeploy) RC1… VS 2010 has great set of features on deploying web applications seamlessly…   One of the key features is the ability to publish...

The new installment of the “CLR Inside Out” column in MSDN magazine is now available on line.  This month we have an article from Subramanian Ramaswamy and Vance Morrison on Memory Usage Auditing For .NET Applications. You can find a list of all “CLR Inside Out” articles here.  As always, please let us know if y...

As we’ve mentioned previously, the .NET ThreadPool has undergone some serious renovations in .NET 4, improvements on which the Task Parallel Library and PLINQ both rely.  Erika Parsons and Eric Eilebrecht are the PM and developer on the CLR team for the ThreadPool, and they’re featured in a great new Channel9 video covering the .NE...

Prior to the .NET Framework 2.0, unhandled exceptions were largely ignored by the runtime.  For example, if a work item queued to the ThreadPool threw an exception that went unhandled by that work item, the ThreadPool would eat that exception and continue on its merry way.  Similarly, if a finalizer running on the finalizer thread threw a...

Everyone has probably dealt with an annoying performance issue at some point or the other. Performance optimization is a hard problem and we could sure use some help from you. We have a survey posted at the CLR and Framework Performance blog over here. The survey contains questions assessing your level of satisfaction specific to .Ne...

And the videos keep coming in! We have Shawn Farkas who works on the security model, talking about the new managed security model. Check out the video here. And then we have Surupa Biswas, from the CLR Code Generation team, talking about the new Targeted Patching work in CLR 4. The link to the video is here.

We exert a good deal of effort ensuring that the APIs we provide are consistent within Parallel Extensions as well as with the rest of the .NET Framework.  This is from many angles, including behavior and general design, but also naming.  So when there are slight differences in naming, it raises questions.One occurrence of such a slight n...

Here’s a simple way to look at it.  On a 4-core machine, take 4 million elements, divide this into 4 partitions of 1 million elements each, and give each of the 4 cores a million elements of data to process.  Assuming that the data and the processing of the data is uniform, that all of the cores operate with the same amount of effective...

Exiting out of loops early is a fairly common pattern, one that doesn’t go away when parallelism is introduced.  To help simplify these use cases, the Parallel.For and Parallel.ForEach methods support several mechanisms for breaking out of loops early, each of which has different behaviors and targets different requirements.ExceptionsIn ...