Maximum PC

Since I haven't been on these here forums, for goodness how long (due to school then working and traveling). I'm gonna try to be more active here, so in lieu of this:

http://msdn.microsoft.com/en-us/concurr ... fault.aspx

What do you guys think about the upcoming .NET 4.0 framework with ParallelFx?

For the newbies Parallelism is executing code in one or more processor cores. Parallelism differs from threading in that threading deals with executing different threads of work (execution code) where parallelism executes a portion of work amongst different processors.

Personally, I'm excited. .NET 4.0 is going to introduce a LOT of power to developers. However, it feels like I'm going to be spending time learning a new pattern for both threading AND parallelism.

If you guys are planning on using .NET 4.0, how do you intend on using it?

We are still writing .NET 2.0 applications here

I need to try to keep up with it. A lot of business I think are "slower" to move to new frameworks.

If I weren't developing for Sharepoint, I'd be on 3.5 right now. I'm using 3.5 on my pet projects. I was using .NET 3.5 and, let me tell you, LINQ will make your life easier.

I love LINQ:


Beautiful man, beautiful.

Haven't used LINQ. Not sure I am a fan of dropping that stuff right in the middle of my code.

Well, LINQ is an umbrella term. LINQ can be used for collections.



It makes finding things inside collections (anything that implements IEnumerable and IQueryable) easier. The examples above do no justice but a good primer on it.

Highly recommended. I use LINQ pretty much exclusively now, it makes writing a Data Access Layer easier and if you use LINQ to SQL, it will generate business objects for you.