Avtually, the AsParallel is best placed onto the source (i.e. tables in your example). Check out my screencasts for how to get started: http://channel9.msdn.com/Showforum.aspx?forumid=38&tagid=269[^] Cheers Daniel

-- http://www.danielmoth.com/Blog

I tend to agree: it sounds like not being with that company was the right result for you - whether by choice or otherwise :-)

-- http://www.danielmoth.com/Blog

I am not sure that this is the best place for support questions (I don't want to upset the moderators), so please use the free online forums for that: http://forums.microsoft.com/MSDN/default.aspx?SiteID=1 Generally though, your understanding is correct. Remember that NetFx3 was going to be Vista-only and after customer feedback it was made to work on XP and WS03 as well... HTH

-- http://www.danielmoth.com/Blog

Please see my reply to John. Also please do not confuse the framework/CLR with the IDE. You are saying that .NET 2 is not stable and then you talk about compilation issues. If you have issues with the IDE/compilers (irrelevant to the framework) then maybe VS2008 will sort them out for you :-)

-- http://www.danielmoth.com/Blog

Thanks for the thoughtful reply John. Please note the smiley, as my comment was meant to be a bit tongue in cheek. IMO, quick subsequent releases are problematic only when they potentially break existing codebases. Even then, it is an opt-in model due to the side-by-side nature of the CLR. Like I said though, the new stuff is all additive (and multitargeting in VS2008 is a huge help). So you need only take advantage of v3 or v3.5 when you actually require it and not a day sooner. As a developer, I think that is a good thing. Happy coding :-)

-- http://www.danielmoth.com/Blog

Well, Jim in Arizona I think if you read my blog posts you'll see that the new advancements are additive which is the whole point. You *can* stick with v2.0 and still use the latest IDE (VS2008) and only use v3 and v3.5 features when you are ready (in the same way you can use your own new libraries when you are ready). No runtime retesting since the CLR is the same and no compatibility issues since the framework bits are additive. Like I said, please read the posts for more info. I never thought I'd hear people complain for too much innovation :-)

-- http://www.danielmoth.com/Blog

Howard Richards wrote:

I would also caution against going to one of his MS presentations - he talks so fast that you really have to concentrate to keep up

That is not true at all! Even if you do concentrate, you still won't be able to keep up with my content-packed sessions :-)

-- http://www.danielmoth.com/Blog